I do not know the answer to the question I asked. In my efforts to obtain feedback on the issue, I have made comments on both sides (pros and cons) of allowing access to some .NET Framework classes from within VFP directly via a COM object wrapper utility that is generic. So far, I've received some very useful replies listing the various .NET Framework classes people would want to call from within VFP directly. Most important is System.Xml, since those classes cannot be subclasses in .NET and therefore you cannot create COM wrappers for them to call within VFP using VS .NET. There may be some benefits of being able to use certain .NET classes from within VFP using a generic COM/.NET interop wrapper rather than having to create specific COM wrappers for each class needed, especially the native .NET base classes.