Two options are available for exporting projects to Silk Performer:
When testing Web Services, .NET Explorer enables you to export Silk Performer Web projects with native BDL scripts (no .NET code is included) that include WebPagePost statements for each Web service call, enabling you to run tests in Silk Performer to test the Web services while making use of the powerful Silk Performer Web engine and features such as TrueLog, statistical reporting, modem simulation, and IP spoofing. All random variables, output variables, and verifications are included in exported scripts.
Your test scenario can be compiled into a .NET assembly that uses the Silk Performer .NET Framework. Silk Performer .NET projects are then created with the compiled assembly and a BDF file that contains the calls to the assembly. In other words, .NET test code is compiled into a .NET intermediate language and then executed through Silk Performer. The value of this is that you can utilize Silk Performer runtime and scripting to make Web calls even though you are running .NET code and not a Web script.
With this intermediate code, when a test case contains Web service calls, the calls are routed over the Silk Performer Web engine so that you can obtain detailed information about each Web service call and make use of features such as TrueLog, statistical reporting, modem simulation, and IP spoofing.