Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
.NET 4.0 framework changes
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows XP SP2
Miscellaneous
Thread ID:
01494618
Message ID:
01494893
Views:
81
>We have an 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 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.
>------------------------------------
>
>I sent an email to eTecnologia asking if a newer version would help but I have no idea when I might get a reply. Right now I have a bunch of customers that can't run payroll.
>I see that West Wind now has a .Net connector also.
>
>Any ideas are welcome. I expect the torches and pitchforks at the door at any minute.

Can you specify the steps you took to install the new DLL ?
Also exand a bit on 'can't get it to work' :-}

Are you now building against .NET 4 (check the project app.config file) ?
Use Gacutil to check if the required DLLs are indeed installed in the GAC (http://msdn.microsoft.com/en-us/library/ex0ss12c.aspx)
If it *is* in the cache then it also should appear in the .NET tab of the 'Add reference' dialog (which should be filtered to .Net Framework 4 or probably .Net Framework 4 Client Profile if this is a WinForms app

IAC if you are building against .NET 4 then there should be no real requirement for the DLL to be in the GAC. Simply add a reference to it by browsing to its location.....
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform