After calling a Web service you can store the returned values to variables and define verifications for those values.
Once you have finished defining your test scenario you can either remain in .NET Explorer, and use your test scenario for functional testing, or you can export the project to Visual Studio .NET or Silk Performer to further customize the generated code and run regression tests.
You can only export to BDL Web projects when your test scenarios contain only Web-service calls, because only WebPagePost statements are generated for each Web-service call. If you have calls other than Web-service calls, for example calls to other .NET objects, those calls will not be included in Web scripts and therefore your exported scripts may not behave as defined in .NET Explorer, as some method calls will be missing.
Only export to BDL Web projects if you have only Web-service calls and if you only wish to test the SOAP stack of your server, as there is no .NET client SOAP stack involved when executing scripts in Silk Performer. The Silk Performer Web engine posts only those SOAP envelopes that have been used in .NET Explorer.
If you also wish to test the .NET client side, you should export your project to a Silk Performer .NET project. This type of project will compile generated .NET test code into a .NET assembly that can be called from a BDL script, which will also be generated by .NET Explorer.
If you wish to make further customizations to .NET code generated by .NET Explorer you can export your project to Visual Studio .NET. If you export your project you can alter generated test code and run a TryScript within Visual Studio .NET. If you are finished with customizations you can export the project to Silk Performer and proceed with testing.