I'm connecting to a web service with a VS 2005 client. It takes a long time (nearly 3 minutes) before the code actually starts doing anything. At first I thought this was a JIT thing going on, but I think that what's actually happening is that custom assemblies are being created to handle the serialization. I know this happens in many serialization cases. A profiler run seems to imply this, as well as the fact that the last line in the debug output text is something like "'SimpleClient.exe' (Managed): Loaded '-squ_ecj', No symbols loaded." where the name of what's loaded is random.
The proxy generated by the WSDL is more than 51k lines of C#. Assuming I've diagnosed this correctly, and keeping in mind that I don't own this web service, is there anything I can do to improve this start-up cost? (Ngen doesn't appear to offer anything to deal with this. ) Phil Wilson =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
