Hi Hao,
Regarding on the ASP.NET webservice responding issue under thousands
method calls, I think you can try using a normal .net 2.0 webservice client
to perform the same test and check the behavior. If the problem is caused
by server-side ASMX service, a normal .net 2.0 service proxy should also be
able to repro it. Also, would you provide the code snippet in your client
application which execute thousands of webmethod calls?
In addition, I'm wondering whether this is a specific behavior occuring at
debugging time. You can set server-side service's <compilation debug="true"
/and test it again(printout webmethod execute timespan) to see whether
the problem still occurs.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
