>I've taken to mostly using clrhost (and modifying if necessary) to support .net from VFP. Found this (while old, good information for starting out) helpful (not to mention your white papers are great for getting started - thanks!!!!):

Yes that's exactly what wwDotnetBridge does. It bypasses the regular COM Interop invokation mechanism and instead loads the .NET runtime directly into VFP with a proxy object to allow instantiation of any type (not just those that are marked for COM export - which are very few).

If you're doing COM Interop with .NET from FoxPro you should have a look at wwDotnetBridge - it brings a ton of additional functionality to the table that is not possible with plain COM Interop greatly expanding the reach of what VFP code can access.

+++ Rick ---

>
>http://msdn.microsoft.com/en-us/magazine/cc163791.aspx
>
>
>
>>You might want to checkout wwDotnetBridge which allows accessing .NET components without registration through RegAsm...
>>
>>It's now free and open source:
>>
>>http://west-wind.com/wwDotnetBridge.aspx
>>
>>and there's a white paper that explains plain COM interop (what you're doing) and how you can do that and much more with wwdotnetbridge:
>>
>>http://west-wind.com/presentations/wwdotnetbridge/wwDotnetBridge.pdf
>>
>>+++ Rick ---
>>
>>>It's been a while since the last time I have done that. I am trying to access a .NET dll from VFP.
>>>
>>>So, I tried this:
>>>
>>>

>>>loFramework=CREATEOBJECT("Framework.CRC32")
>>>

>>>
>>>But, I get "Class definition FRAMEWORK.CRC32 is not found.".
>>>
>>>I recall there is something I have to do in .NET to expose the class. I don't recall if there was anything additional to do at the VFP level or the register of the dll.