Hi,

I have a requirement to call a WSE 3.0 web service from an ASP.NET 2.0 application. The full web service is being written by a third party, and is not yet complete, but the interface is defined. In order to facilitate testing on the ASP.NET consuming application, I've written a stub web service with the same interface; this is currently running on my development box under IIS (along with the ASP.NET consuming application) which is XP Pro and IIS5.2.

This all works very well, with one exception ... the return from a web service method call takes upwards of ten seconds, and not just on the first call. Using VS Debug, it seems the problem is at the point of return from the web methods - the actual call into the method and its processing is executing in a reasonable time. As I need to call the service for each line in a DataGrid, this is a bit of a problem - it can take 2 minutes or more to populate and display the affected pages. When I call the incomplete remote (third party) web service over the Internet, it's pretty quick.

I've seen Rick Strahl's article (http://www.west-wind.com/WebLog/posts/3871.aspx) regarding default proxy behaviour in ASP.NET 2.0, and have changed the service consumer's web.config as indicated, along with various other permutations, but this seems to make no difference.

If anyone could shed any light on this problem or has any suggestions as to how to isolate the problem, I'd really appreciate it.

Thanks,
Graham