Vision Acquisition Odd behavior with NationalInstruments.common assemblies

[wbadry]

Hi,

I have installed Vision Acquisition 2010.08 and Measurement Studio 2010. The problem I had earlier as NationalInstruments.common assembly that is shipped wih the new version doesn't have dependecies (like those used in IMAQdxSession class for instance).

I wonder when both teams pay attention to such a problem. The reommended is always to use the latest assembly with is reasonable. However, I always get errors in functions that unfortunately require functions only available in the previous releases.

As I mentioned earlier, I have the latest versions, but it sounds that they don't work with each other. Is there any remedy for such a problem?

[jdubs]

Waleed,

Can you give a specific example of the errors that you are getting and how you get them?  What combinations of Vision and Measurement Studio have you used in the past that have worked?  What version of Visual Studio are you using?

Thanks for the additional information!

Jen W

Applications Engineer

National Instruments

ni.com/support

[wbadry]

Thanks Jen for your response,

Briefly mentioning once again the instaled software:

• Vision Acquisision 2010.8 (August which is the latest)
• Measurement Studio 2010
• Visual Studio 2010 Professional Edition
• Vision Development Module 2010

Since measurement studio 8.6 was previously installed, NI measurement studio asks to update the measurement studio common assembly which I accepted and the problems strated to arise.

1. The grab function in IMAQdx class keeps demanding an older version (8.7 or something alike through the error tage of visual studio even though the lastes assembly is added which is newer).
2. IMAQdxSession asks for the same as the previous one.

I tackled the problem by adding the measurement studio common assembly of previous version. However, it keeps me wondering, how come that the nerw version has a different assembly to the same methods. Did we get back to "the DLL Hell" problem?

Hope the development team could yield a rartional explanation to the problem.

[nickb]

Hello -

The primary issue here is that Vision 2010.8 does not have support for Visual Studio 2010.  This means that if you are using Measurement Studio 2010 components in Visual Studio 2010, you will have a dependency on the 4.0 runtime version of Common, whereas your Vision libraries will have a dependency on the 2.0 (presumably 3.5 framework) runtime version of common.  Because we only policy assemblies that target the same .NET Framework version (8.7.35.xxx won't be policied to 9.0.40.xxx), you are running into the errors you've reported.

Unfortunately, for the time being, there's not a clean way to use the Vision libraries in VS2010.  The best way to do it and still use Measurement Studio components is to install Measurement Studio 2010 for VS2008 and reference those libraries (9.0.35.xxx) in VS2010, instead of using the native VS2010 libraries.

NickB

National Instruments