>I'm jumping a little late in this conversation, but I'd like to point out namespaces that I am interested in:
>
>Scenario 1 System.Drawing:
>A software solution that is composed of a .Net app (ASP.NET) and a VFP app.
>There are classes built for the asp.net application using the System.Drawing namespace that the VFP app could use, thus, we would avoid to rewrite the whole thing in VFP, and only would concentrate our efforts on building the front end in VFP.
>
>Scenario 2 System.Xml:
>A software solution that is composed of Two win32 apps, one .NET the other one VFP: The .Net app uses complex nested xml files for app configuration purposes. I would like to create a user interfase in VFP using System.Xml in order to handle and generate the same kind of nested xml files. I know VFP 9 handles some nested xml files, but I couldn't do it with the ones we use and generate from the .NET app.
>
>Scenario 3 System.Web.Services.WebService (I guess at some point System.Data could be needed as well, not quite sure of this yet):
>I had web services built in vfp using SOAP running in WinNT/MTS environment. The server was upgraded to Windows 2003. We couldn't make them work in the COM+ environment, unexplainable errors wouldn't even let us install them. Decision was to rebuild the web services using .net (specially considering MS advising us against using SOAP web services with W2003 in the long run because of the limited support for VFP/SOAP 3), which is fine for me, but what if we could use this namespace from vfp, then I keep things in the vfp 9 platform and could also assign this work to one of the 'in house' VFP developers instead of hiring a .net one.
>
>Do these scenarios make sense to you ?

Yes, this is "exactly" the type of feedback I am looking for, thanks!