As the bottom of WebService, SOAP has made great contributions in the period of non-hosting code calling WebService, but with Microsoft, the more far from .NET. The development of SOAP Toolkit also stopped. Since technical support for SOAP Toolkit is about to expire, I guess the recently released SOAP Toolkit 3.0 (
http://www.microsoft.com/downloads/details.aspx?familyid=c943c0dd-ceec-4088-9753-86f052ec8450&displaylang=en) should be the last version of this software.
Articles in MSDN
Migrating from the Microsoft Soap Toolkit to the .net framework and
INTEGRATING Web Services and Comssents These two articles can help to transplant the application from SOAP to .NET. Of course, the non-hosting code can also call WebService by hosted functions, using Managed C in Visual C to easily do this (#pragma management / # pragma unmanaged). It is necessary to consider the performance overhead generated between the non-hosting code and the hosted code.
Never say never. SOAP life period is definitely longer than Microsoft's support period, as for how long, who know?
