>Ok, to continue with this matter, I can confirm that any COM+ component can be automatically published as a web-service without the need of the Soap Toolkit on Windows Server 2003 (and I learned it last week, a bit late).
>
>The bad news is that apparently Microsoft decided to quit this really good thing to replace it with WCF. I hate them :_(
>
>https://social.msdn.microsoft.com/Forums/sharepoint/en-US/c37ac0cb-96c7-405e-8acc-64061afa2e5f/com-as-xml-web-services-on-windows-7-uses-soap-setting?forum=windowsgeneraldevelopmentissues
>
>I suppose that nobody have any new info about it...

You can use COM objects with both classic ASPX Web Services and WCF using COM Interop in .NET. COM+ might be the way to go but it will slow your components down drastically. Otherwise you can also use raw FoxPro components but there's some extra setup you have to do to account for STA marshalling.

Here's an old blog post of mine that talks about how you can use STA hosted COM components in various .NET technologies.
http://weblog.west-wind.com/posts/2012/sep/18/creating-sta-com-compatible-aspnet-applications

I've built a number of Web Services for customers with ASMX style services and that's worked very well in terms of performance and administration.

In case you're coming to Southwest Fox this year - I'll be doing a session on hosting and consuming Web services in Visual FoxPro using .NET as the intermediary.

+++ Rick ---