Rank: Member
Joined: 2/6/2008(UTC)
Posts: 55
|
When creating the proxy object, NOT the reference, but the actual object,
WebServices3 proxy = new WebServices3()
Is taking like 30 seconds to create this object, typing up all my resources and using like 100mb of ram...
What the heck? The only thing i could think of was it was generating the Serializing assembly, so i changed the "Generate serialization assembly" to ON. Which does infact generate the DLL but my app still is taking ~30 secs to create the web service proxy object.
Anyone else experience this?
Thanks
Ryan
|
|
|
|
|
|
Rank: Member
Joined: 11/5/2003(UTC)
Posts: 2,136
Was thanked: 1 time(s) in 1 post(s)
|
You can use something like SysInternals Process Monitor to find out what is taking so long, but I suspect it is not using your pre-built serialization assembly. The serialization assembly is quite large (~6MB), so it may just take a long time to JIT it and load it into memory.
One option is to create your own web service with just the subset of webmethods that you use. |
|
|
|
|
|
|
Rank: Member
Joined: 2/6/2008(UTC)
Posts: 55
|
Andy,
Have you written any apps that use WebServices3 using .NET? is this a problem for your customers?
Creating my own subset service is exactly what im doing at the moment, just think its kinda silly i should have to :(
Thanks!
|
|
|
|
|
|
Rank: Member
Joined: 11/5/2003(UTC)
Posts: 2,136
Was thanked: 1 time(s) in 1 post(s)
|
Yes. Not much of a problem for the person running the app. The serializer is only built once for them. It is a problem for you and me because the serializer is built every time we rebuild the client assembly.
In my latest project (Shipper 3), I decided to write my own web service that is linked to the Core assembly. |
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.