>Well, there's a little more to it than calling a COM object. Why does a Foxisapi type solution get into the docs and not a VFP .COM interop type solution? Has something changed with the VFPT and their direction - again I don't think anyone will blame you for being honest here. Is it because you just don't want to go in that direction or a lack of resources? I'm just looking for a straight answer.

This is not about resources. Foxisapi was a component included with VFP, and each component and feature of VFP is documented in the VFP help files. Visual Studio nor the .NET Framework is not included with VFP, so how those products work together is not in the VFP documentation. msdn.com is the place for these topics, just like topics such as using Visual Basic with Office, etc.