>>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.
>
>Yes, once inside the WS, an XML call is being issued to our WWC VFP server. So, WS, as I think it should be, has been done as a wrapper. There is no business or data objects in it. However, I had to deal with a lot of things such as preserving the cookie, establishing the XML connection with the other tier, date conversions, replacement of the COMRETURNERROR() and so on.

Hi Michel,

Following up on Ken's encouragement, what do you think? Would you be interested in putting together a piece about UT's successful migration into the .NET framework?

You might have a decent shot at getting this into MSDN Magazine and/or some other very conspicuous places, making great PR for all concerned. I'd be glad to help, if I can, and I think you'd have no trouble getting additional help, if you need it. Maybe Ken could point you to some receptive editors and put in a good word for you.

Mike