Well, there are, and have been for a while, multiple entries in the documentation and many examples of Foxisapi(even though this solution is not even advocated by MS anymore). Why not the same thing for VFP .NET interop(COM interop,mtdlls, XML, etc)? Create several examples and put them, and any special notations, in the the documentation. Again, I don't see how this could be any simpler...
>As you can see in the entire VFP documentation, how to build applications is not included. What is document is specific features in the product. Can you be more specific about what exactly you would like to see online that is not already available for people to read and learn about? While we don't rely on 3rd parties to create information on specific topics, when we see good material from 3rd parties then we will probably not try to create the same material and instead focus on something else. I would be glad to help efforts to create more material on VFP and .NET interop based on demand, but more specifics on what you and others think is needed would be helpful. Most whitepapers we have on VFP are created by 3rd party VFP developers, they are the experts on creating solutions in the real world with VFP. Our expertise is creating the product and tools, not the solutions for applications.

>>Just examples and documentation of VFP .NET interop in the actual vfp product. I don't see how this can be any simpler. Why do developers need to rely on whitepapers from 3rd parties for key technologies?? I could hardly find anything about this in the VFP 9 beta. Forget about new tools - just improve what we can do now so we can use the strengths of both development environments...
>