Re: Will DotNetBridge work witn .Net 4? We have big probelms

Rick, I've got a very simple .NET class I'm trying to call using wwDotNetBridge. The .NET class is targeted to the 4 framework. When I follow your example code of loading my DLL, I get the error message:

Could not load file or assemply 'file:///c:\wconnect\mysample.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

I tried passing in an explicit "V4" as you mention but it still gives the same error message. I'm running this on a machine that has VS 2010 installed so I assume that V4 is the "currently loaded runtime". I guess wwDotNetBridge is loading some version other than V4 for some reason?

Any suggestions.

EDIT: Scratch that. I just retried everything using your latest 1.21 build of West Wind Web Proxy Generator and it seems to be loading the assembly now. I was able to use InvokeMethod to access my static method.

John,

Yes the wwDotNetBridge works with .NET 4.0. You can specify the runtime version when you instantiate the object...

loBridge = CREATEOBJECT("wwDotNetBridge","V4")

Nothing needs to be in the GAC or otherwise installed, but I'm sure the syntax for accessing .NET components will be a little different than the eTechnologica stuff.

+++ Rick ---

I see that West Wind now has a .Net connector. Do you think it can handle this?

We have a VFP 9 interface to a .Net payroll program that, for the past three years, has worked without a problem allowing us to exchange data in both directions. We are using .NET Extender for VFP from eTecnologia and it has work very well. We just referenced the ActiveX and all worked Ok.

The payroll company has just updated their software to use the .NET 4.0 framework and now nothing works. They sent me a new SDK but I can't get it to work. Here is what they said to do in VB.

------------------------------------
As you probably know our software is installed in the Global Assembly Cache (GAC). For 2011 we upgraded our program to use the .NET 4.0 framework (client profile). Microsoft decided that assemblies based on the 4.0 framework would be installed in a new, entirely separate GAC. Client programs that reference our dll will automatically find the right one but they have to first reference the right one.
The bottom line is that you must download the latest version of the sdk, re-reference the dll, and recompile your program.
------------------------------------

Right now I have a bunch of customers that can't run payroll and I expect the torches and pitchforks at the door at any minute.
Thanks

---