.NET 4.0 Support

[nickb · Accepted solution]

Hello,

We've reproduced the error you're getting, but we have not yet identified the cause of the error.  I've filed a bug report with ID 283358 to continue investigating this issue. 

While investigating this, I was not actually able to reproduce the error you saw.  However, a colleague of mine was able to reproduce the error. 

- I was able to generate the wrapper for your assembly from CVI 8.5, 9.0, and 2009 on my machine. 
- My colleague saw the same error as you saw with all versions of CVI on his machine (8.5, 2009, etc). 

Is your CVI 8.5 installed on a different machine that your CVI 2009?  If so, could you try installing CVI 8.5 on the machine with CVI 2009?  It's possible that this error is machine dependent.

Finally, I've attached the 8.5 version of the wrapper that I was able to generate on my machine.  If your assembly isn't going to be changing much, this should work for you.  Otherwise, you'll likely need to generate the wrapper from 2009 (or on that other machine) until we're able to determine the cause of the error.

Sorry for any inconvenience -

NickB

National Instruments

[Ivan Muzzolini]

, 2003Hi!

CVI 8.5 and CVI 2009 are on different machines.

• CVI 8.5 is on my work machine (Windows XP SP3) together with several versions of .NET (1.1, 2.0, 3.5 and 4.0) and several versions of Visual Studio (2003, 2005, 2008 and 2010).
• CVI 2009 is on a virtual machine (Windows XP SP3 on Oracle VirtualBox 4.0) together with VS2010 and .NET 4.0 framework only.

Just yesterday, on my work machine, I've installled also the LabWindows\CVI 2010 runtime, I compiled my project with the wrapper, added the <>.exe.config and the app is working.

Due to the fact that on my vm I can generate the wrapper, I would prefer to keep it as it is.

In any case, I wait for news regarding possible fixes to this issue!

Thank you very much!

Best Regards

Ivan Muzzolini

Electrolux

[nickb]

Hey Ivan -

After continuing to look into this issue a little further, it turned out that there is a bug in CVI 8.5 that was fixed for all future versions.  The bug isn't actually a result of any implementation detail, but because we built some of our internal components against the .NET 1.1 Framework - without SP1.  The error you were seeing was a result of assemblies built against a pre SP1 version of .NET 1.1, and because we built against .NET 1.1 SP1 after 8.5, the issue is no longer present.

To get the updated, working, components, you just need to install a version of the LabWindows/CVI Run-Time Engine later than 8.5.

NickB

National Instruments