Hi,

I'm calling an exposed method of a .NET DLL via (regular/old) ASP using
COM Interop.  This method that I'm calling then calls a .NET web
service.

Note that this web service I need to call does not yet exist but I am
testing error catching routines to make sure potential errors are
handled gracefully.

I have code in this method to catch exceptions--particularly a
"System.Net.Sockets.SocketException" exception (to handle a scenario
whereby I cannot connect to the web service).  I have made a test shell
with VB 6 and the error is caught as expected and handled accordingly.

However, when I access the method in question via ASP, the exception
does not seem to be caught as it should and the ASP app crashes.

Is there some kind of limitation involving COM Interop, ASP, and .NET
Web Services involved here that anyone might know about?

Cheers,

Mike.