VisaNS.dll depends on old Common.dll

[Tetsu]

Hi,

I'm using VS2010 with NI Measurement Studio assemblies. I downloaded ni4882_302.exe that seems to be the latest as of writing and compiled the SimpleReadWrite sample project in the NI-VISA\Examples\DotNET4.0 directory after having replaced the NationalInstruments.Common reference from the older 9.0.40.362 to the latest 9.1.40.159.

Then I got the following warning message - "Found conflicts between different versions of the same dependent assembly". Changing the VS2010's "MSBuild project build output verbosity" in Tools/Options/Projects and Solutions/Guild and Run dialog from Minimal to Detailed, I finally understood that the VisaNS.dll (9.0.40.156) does depend on the older Common.dll (9.0.40.362).

VS2010 suggested modifying the app.config file to remap the assembly reference to solve the issue, but I don't want to do it to fix seemingly a defect that was introduced when the VisaNS dll was compiled at National.

What other options do I have to solve the issue?

Thanks,

Tetsu

[0utlaw]

Hello Tetsu,

It may be necessary to repair the installation of Measurement Studio after manually updating NationalInstruments.Common, which I believe is what you've described - doing this should allow MS to recognize the update. The instructions here outline how to repair a LabVIEW installation, but the same process can be used to repair Measurement Studio.  If you are still seeing this behavior after the repair, all releases of Common are backwards-compatible, so if the warning is the only issue you are seeing, you should be able to safely ignore it.  If there are other problems associated with this warning, however, please let me know and I may be able to offer further advice.

Regards,

[Tetsu]

Tom,

I uninstalled the NI software, removed all NI assemblies from GAC, deleted the sample projects placed in the Public Documents directory, and re-installed ni4882_302.exe.

Then, I opened the SimpleReadWrite project sample and got two compile errors because the referenced Common.dll is not found. I think that this simply is a defect of the package; the user can't compile sample projects.

Removing the old Common reference and adding the new one of course solved the compile error but came with the warning - Found conflicts between different versions of the same dependent assembly.

I haven't yet seen side-effects other than that warning message, but I'm not comfortable. I accept the knowledge base article's statement - It can also occur when your project references assemblies that depend upon versions of NationalInstruments.Common older than the latest version installed on your machine. But the project is not mine, but yours.

Tetsu

[0utlaw]

Hello Tetsu,

I have validated this behavior on several test machines, and have reported the issue to R&D (# 350698) for further investigation.  Thank you for making us aware of this, and please let me know if you encounter any other issues with the driver example projects.