Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

What issues were fixed in SilkPerformer 6.5?

What issues were fixed in SilkPerformer 6.5?

  • When a script (.bdf) file will be compiled, all "modified and still not saved" .bdh files, that are included from this script file, must be saved manually before compiling the script. All .bdh files are now automatically saved.



Performance Explorer:

  • After moving some toolbars of SilkPerformer Performance Explorer into a floating position, opening a workspace file may cause different problems in some cases because of incorrect information about the Toolbar-ID"s in the registry and in the workspace file. Possibly the file cannot be opened, or the Performance Explorer may crash when opening a workspace file.



  • When remerging tsd files, the average user group results in the overview report are incorrect if the remerge changes the time frame.User group data are now dropped, if the remerge changes the time frame.


.NET Support:


  • .NET Explorer projects that test Web Services, and have NULL value verifications defined for return values of Web Service calls, are exported incorrectly if exported as BDL Web Project. An incorrect BDL function call is generated in the BDL script that will be exported.


  • A verification on a method that returns no value (void) can be defined in .NET Explorer. This shouldn"t be allowed as a void value cannot be verified against any value. If a verification is defined on such a value and the project is exported to Visual Studio .NET or as SilkPerformer .NET Framework project, an uncompileable C# or VB.NET code is generated.


Java Support:

  • Local variables are stored under the context of their testcase. If the name of a testcase is changed, the scope of the variables is not updated and so any local variables are lost.


Web Support:

  • The SSL handshake may fail when using client certificates (typical error message: Security: 267 - wrong version number, SSL Connect).


  • For special cookie path and URL combinations some requests may not send all required cookies.


  • A special combination of characters in an URL may let the url parser crash (used for recording, replay and in the TrueLog Explorer).


  • Recording the reception of big objects may last a long time.


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:51
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.