http://msdn.microsoft.com/library/default.asp?url="">
>Note In addition to being provided with the Office XP Web Services Toolkit 2.0, the SOAP 3.0 DLL is also included in the SOAP Toolkit 3.0 along with a user guide.
And I assumed that the SOAP Toolkit 3.0 is part of .Net... I thought the benefit of using MS platform was conformity across all of their tools? I guess that's not even possible in MS land! :-)
Gene
Steve Loughran <[EMAIL PROTECTED]> wrote:
----- Original Message -----
From: "Gene Chuang" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 01, 2003 19:12
Subject: Re: Interoperability Axis with .NET (C#)
>
> I just created a web service with Axis 1.1beta for a RPC method that
returns an array of JavaBeans.
> I installed Office XP WS Toolkit 2.0,
http://www.microsoft.com/office/developer/webservices/toolkit.asp, and by
just supplying the WSDL generated from above, MS VB generated the correct
client stubs without my interference. The only caveat is toolkit is not
.NET, and the code is not VB.NET, so the JavaBean array was represented as a
"variant" in VB, a type that has been deprecated for VB.NET ;-).
> However, since the Office XP toolkit 2.0 uses the same soapclient30.dll as
.NET platform, I don't see how .NET wouldn't be able to interop just as
easily as the toolkit did.
.net doesnt use soapclient30.dll, which is part of the MS Soap Toolkit; .NEt
has its own implementation(s) of SOAP. So you cant guarantee that just
because the native code toolkit works. the .NET one will
