>PMFJI and for maybe naive question. Could you describe a small practical example of where you would load .NET from VFP?
>Thank you.
I use it for a lot of things:
* West Wind Html Help Builder imports .NET libraries using Reflection
* Web Connection has the wwSmtp class that uses System.Net.SmtpClient
* West Wind Web Service Proxy Generator generates .NET proxys then calls them to call Web Services
(even without the generator calling .NET generated Web Service clients is a very common use case)
* Multi-threading - if I need something to run Async I have ThreadRunner that marshals the code through .NET
Lots of things. wwDotnetBridge also lets you access arbitrary .NET objects and static functions and properties directly from FoxPro code which expands the use case for .NET to just about anything that .NET can do. You can choose from creating code of your own in .NET and then calling that from FoxPro, or call .NET framework libraries that exist as is.
+++ Rick ---
>
>>
>>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.
