Ciao, Andrea.

>do you know what does it means this ?
>
>.. SOAP Toolkit support will be retired in April 2005.
>
>AND
>
>...SOAP Toolkit support will be retired in March 31, 2005. Extended support will retire in March 31, 2008
>
>Which future for VFP web services ?

The future for VFP Web Services is .NET. Right now it is very easy to publish your Web Service by using Visual Studio 2003, using the same DLL you would usually publish through the SOAP Toolkit. You ust need to add a reference to the COM component and then forward the calls to it, duplicating all the COM methods as WebMethods in VB.NET or C# (or J#, or Cobol.NET or any language you want).

Part of the Sedna effort is geared to simplify these tasks, so maybe you could guess a replacement for the current wizard that generates the proxy and help making the publishing without the need to have Visual Studio.

I just presented a session about this a week ago at DevTeach. The good thing about leaving the SOAP Toolkit behind and going to .NET is that you'll have a lot more features available, like the chance to use WSE 2.0, and soon WSE 3.0 and Indigo at some point in the future.

Also, the SOAP Toolkit never worked terribly well.

Best regards,