On Sat, 18 May 2002 08:25:49 -0700, in soap you wrote: > >----- Original Message ----- >From: "Volanis, Alexander" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Thursday, May 16, 2002 9:51 AM >Subject: RE: [BUG] Beta2 interop (was RE: Interoperability issue with >MSVC++.Net) > > >> >> Chris, >> >> >> >> I am glad there is at least some discussion on this. I agree that the >> >> namespaces are not explicitly required to be the same. This issue >exists >> >> only with the VC++.Net proxy generator. The C#.Net and VB.Net are not >> >having >> >> any issue with either one of the problems I outlined. >> > >> >which one: WSDL.EXE or SOAPSUDS.exe? >> >> SPROXY.EXE is the VC++.Net proxy generator that has trouble here. >> WSDL.EXE is able to operate without problems. > >sproxy? There is a third dotnet WSDL to code generator. Well I never. Two >SOAP stacks, three proxy generators... .NET must be the only framework to >have internal interop issues. > >-steve
ROTFL !, sproxy.exe is the proxy generator for the SOAP support in ATL7, [native C++ code], rather than the managed platform [i guess that's the problem when you stick .NET on the end of everything], so that's actually 3 soap stacks, and 3 proxy generators. There's no ATL server in the soapbuilders interop anymore, but i seem to recall it had a few issues. Given that's its not getting any interop testing, i wouldn't go near it. Cheers Simon
