Web Service / Authenticating Proxy Server

Web Service / Authenticating Proxy Server - COM interop vs. .NET

microsoft.public.dotnet.framework

25 Jan 2006 2:17 AM

whoareyou

Hi,
I have a C# Web Service component I call 2 different ways:
- For testing I have a "pure" .NET solution. A C# test harness app
invokes my C# component.
- From the "real" application, a native C++ app, I call the C#
component via COM interop.

My all .NET test harness has a 407 error returned to it from the web
service component when I don't supply credentials for the proxy server.
The real app, using COM interop, results in an underlying connection closed
error that I've seen written about many times Anyone know why the
difference? this is under framework version 1.1.

Is the "underlying connection closed" error really only a defect seen when
you go native to managed as in COM interop?

Also, when I test the COM Interop solution under version 2.0 of framework
with invalid credentials (hoping to get the improved proxy handling) I never
get a response. The application just hangs. I can't even cancel the request.

The above is all implemented as asynchronous using the Begin... and End...
semantics.
Thank you