>>I'm impressed. The migration of the Universal Thread Web Service in .NET took 8 hours. I received a lot of help today from Universal Thread. But, in overall, it went well.
>>
>>What I like the most is that I don't have to create a context anymore as this is already builtin. I also do not have to deal with ISAPI or ASP listener. It is faster and all that which much less code. But, the most interesting part, I didn't have to connect on VPN to the server to register a DLL, compile the Web Service, update the ASP listener file and test it. Everything has been done locally and only by FTP, I was able to upload my ASMX, the DLL files and that's it.
>
>This is great news. I've been promoting the use of ASP.NET as an interface to VFP for XML Web service rather than using VFP XML Web services directly for the service. Just use ASP.NET + VFP COM instead of creating an XML Web service in VFP directly to allow ASP.NET interface with IIS rather than VFP. You can now go into the ASP.NET layer and change any type of functionality you want while leaving the VFP COM DLL alone, a much better solution. Keep us posted on your progress.

Here's a thought, Ken. Michel's success story putting of VFP together with .NET would make a great case study for getting another article into one of the major MS pubs. I'll bet Michel could drum up a lot of very talented help with the writing. I haven't discussed it with him, but Michel might see it as a great opportunity for promoting UT.

What do you think, is it worth a shot?

Mike