In
Silk Performer, expand the
Profiles node in the
Project tree.
Right-click the profile that you want to configure and choose
Edit Profile.
Tip: Alternatively, you can choose
Settings
> Active Profile from the menu bar.
The
Profile - [<profile name>] dialog box opens, and the
Replay category is displayed in the shortcut list on the left.
In the shortcut list on the left, click the
.NET icon.
Check the
Route HTTP .NET through
Silk Performer web engine check box to route all HTTP/HTTPS traffic that is generated by your .NET test driver through the
Silk Performer Web engine.
This allows you to take advantage of the features that
Silk Performer offers for accurate testing, such as its high performance Web engine, modem simulation, detailed timing/throughput information
for each transmission, HTTP/XML TrueLog, and IP spoofing.
The
Routed web service proxy classes text box displays the .NET Web Service client classes that are used in your .NET test driver. HTTP/SOAP traffic of selected
classes is routed through
Silk Performer’s Web engine, regardless of the setting above. This setting can only be changed via the
Silk Performer .NET AddIn.
Click the
One application domain for each virtual user container process option button to share one .NET application domain among all virtual users running in a virtual user process.
This minimizes the administrative overhead for the .NET Common Language Runtime, but may cause runtime problems because all
objects will be loaded into the same application domain.
Click the
One application domain for each virtual user option button to give each virtual user its own .NET application domain.
This increases the administrative overhead of the .NET Common Language Runtime, but ensures that objects from different virtual
users will not interfere with one another.