Wooops... :-)

Options for that are a lot more limited - creating VFP COM objects and referencing with the dynamic keyword is the best choice.

+++ Rick ---`

>RIck -
>I think the post is asking the opposite question :
>i.e. calling VFP com from C#........
>
>>
>>You can create .NET COM components that let you call C# code from FoxPro. It requires that you compile your .NET components with the COM Interop flag in the compiler options which enables your components to become COM callable from VFP.
>>
>>That works, but it requires COM registration (actually .NET COM registration which requires special tools) and you don't have access to .NET components that are not explicitly exported to COM. Most .NET components are not accessible via COM.
>>
>>There are also ways to bypass COM registration for .NET components by hosting the .NET runtime in FoxPro. This also gives the opportunity to access MOST .NET components from FoxPro including those that are not directly supported via COM Interop.
>>
>>I wrote about this here:
>>http://www.west-wind.com/weblog/posts/2007/Jul/01/Hosting-the-NET-Runtime-in-Visual-FoxPro
>>
>>Or you can look at the West Wind Internet and Client Tools which integrates this functionality directly into a wwDotnetBridge component.
>>
>>Here's more info on the actual wwDotnetBridge class:
>>http://www.west-wind.com/webconnection/wwClient_docs/_24n1cfw3a.htm
>>
>>Hope this helps,
>>
>>+++ Rick ---
>>
>>>Hi all
>>> I want to make a DLL from VFP for user C#.
>>>I have a class in VFP and I build a DLL with “Single -Thread Com Server” and “Multi -Thread Com Server”. The files DLLs distributed to user C#, but user C# cannot add in project.
>>>
>>>Please help me or show me how to do that. Thanks.