Problem with instanciating proxy class

[Andrew Jackson]

Hi all...

My app is a .net2 winforms app written in c# using visual studio 2005.

I have added a web reference to (what I consider) a fairly large web
service. When I try to use the web service in my client application via the
autogenerated proxy class, the first time I instanciate my proxy class, it
take almost 3 minutes for the call to complete. all subsequent calls are
instant. this delay is before any actual calls to the web methods.

e.g:

WsProxy.Journey DataServices proxy = new WsProxy.Journey DataServices(); <--
this line causes the problem
WsProxy.Custome r[] items = proxy.GetCustom ers();

I can load the webservice url in a browser and have noticed no problems
there (database connection is working, no obvious security problems, etc)

I understand that the first time the proxy call is called it might cause a
small delay because of JIT compilations and serializers, etc but is 3
minutes really a realistic time for this process? I have tried running
sgen.exe on my assembly but it did not seem to product any significant
reduction. maybe i;m doing something wrong?

Any ideas anyone?

Thanks,
Andrew

[Andrew Brook]

Perhaps the webservice is to blame for the delay?
If the webservice shuts down after a period of innactivty, and if it does a
lot of work on startup (caching data etc).

"Andrew Jackson" <aj******@eccc. co.zawrote in message
news:er******** **@wblv-ip-nnrp-1.saix.net...

Hi all...

My app is a .net2 winforms app written in c# using visual studio 2005.

I have added a web reference to (what I consider) a fairly large web
service. When I try to use the web service in my client application via
the autogenerated proxy class, the first time I instanciate my proxy
class, it take almost 3 minutes for the call to complete. all subsequent
calls are instant. this delay is before any actual calls to the web
methods.

e.g:

WsProxy.Journey DataServices proxy = new WsProxy.Journey DataServices();
<-- this line causes the problem
WsProxy.Custome r[] items = proxy.GetCustom ers();

I can load the webservice url in a browser and have noticed no problems
there (database connection is working, no obvious security problems, etc)

I understand that the first time the proxy call is called it might cause a
small delay because of JIT compilations and serializers, etc but is 3
minutes really a realistic time for this process? I have tried running
sgen.exe on my assembly but it did not seem to product any significant
reduction. maybe i;m doing something wrong?

Any ideas anyone?

Thanks,
Andrew

[Andrew Jackson]

I found a solution from information gleamed from this page:
http://www.vmware.com/community/thre...ssageID=581599

cheers
Andrew
"Andrew Jackson" <aj******@eccc. co.zawrote in message
news:er******** **@wblv-ip-nnrp-1.saix.net...

Hi all...

My app is a .net2 winforms app written in c# using visual studio 2005.

I have added a web reference to (what I consider) a fairly large web
service. When I try to use the web service in my client application via
the autogenerated proxy class, the first time I instanciate my proxy
class, it take almost 3 minutes for the call to complete. all subsequent
calls are instant. this delay is before any actual calls to the web
methods.

e.g:

WsProxy.Journey DataServices proxy = new WsProxy.Journey DataServices();
<-- this line causes the problem
WsProxy.Custome r[] items = proxy.GetCustom ers();

I can load the webservice url in a browser and have noticed no problems
there (database connection is working, no obvious security problems, etc)

I understand that the first time the proxy call is called it might cause a
small delay because of JIT compilations and serializers, etc but is 3
minutes really a realistic time for this process? I have tried running
sgen.exe on my assembly but it did not seem to product any significant
reduction. maybe i;m doing something wrong?

Any ideas anyone?

Thanks,
Andrew