J
Jerry
Dear friends, I am amazed with this estrange behaviour. Hope you
believe this is happening to me.
The case:
1. A simple Web Service with a single method returning a constant
quite big string (120KB), for performance test purposes (requires
authentication).
2. A simple client that calls 10 times this web service:
Sample Code:
mObjectWS = new TestMonitor.TestMonitorWS.TestWS();
mObjectWS.Credentials = new
System.Net.NetworkCredential(txtUser.Text, txtPassword.Text);
for(int i = 0; i < 10; i++)
{
string res = mObjectWS.DemoString();
}
Results:
If I run the client from the Visual Studio IDE (F5) it takes about 500
ms.
If I run the client outside the Visual Studio (double clik over the
..exe file or CTRL+F5) it takes about 5000 ms.
In both cases the job is done.
How can it be possible? Is Visual Studio skipping steps, or is the
..exe repeating unnecessary steps?
Thanks in advance,
Jerry
believe this is happening to me.
The case:
1. A simple Web Service with a single method returning a constant
quite big string (120KB), for performance test purposes (requires
authentication).
2. A simple client that calls 10 times this web service:
Sample Code:
mObjectWS = new TestMonitor.TestMonitorWS.TestWS();
mObjectWS.Credentials = new
System.Net.NetworkCredential(txtUser.Text, txtPassword.Text);
for(int i = 0; i < 10; i++)
{
string res = mObjectWS.DemoString();
}
Results:
If I run the client from the Visual Studio IDE (F5) it takes about 500
ms.
If I run the client outside the Visual Studio (double clik over the
..exe file or CTRL+F5) it takes about 5000 ms.
In both cases the job is done.
How can it be possible? Is Visual Studio skipping steps, or is the
..exe repeating unnecessary steps?
Thanks in advance,
Jerry