Ok. I for one won't be upgrading to any more vfp versions because of the dramatic de-emphasis of .NET interop, web services, web applications etc. in the product. For me these were the important areas to keep VFP alive with the newer technologies ...

>Your assumptions are completely false and imaginary. We have never put extensive samples in the VFP docs of VFP working with other products, the documentation is about the features and functions of the product only. We post content online for application centric solutions, not in the docs. You can see links to whitepapers and download several samples involving VFP and .NET interop at http://gotdotnet.com/team/vfp which is a section focusing on VFP and .NET working together.

>>My closing comments on this subject: Ken has said no to documentation, examples, etc. for vfp com interop with .NET regardless of the need from developers in this area. I think the real reason behind this is that he would rather have VFP developers converting to .NET and developing VFP type solutions for .NET projects. IOW, he wants the mindshare of VFP developers going to new .NET projects to benefit this area of .NET development which he is also involved with rather than using .NET interop and taking advantage of the strengths of both products. Again, just my opinion, but, it seems to make sense as far as his actions or inactions...
>