NIDAQmx 8.3 .NET assembly dependency discrepancy

[MatthewZ]

I just updated to the 8.3 NIDAQmx drivers. Apparently, this update installed a new NationalInstruments.common.dll. When I compile, I'm getting a warning that appears to be comming from NationalInstruments.Analysis.Enterprise.dll Here's the warning text:

---Begin Include
3>Consider app.config remapping of assembly "NationalInstruments.Common, Culture=neutral, PublicKeyToken=4544464cdeaab541" from Version "8.0.20.270" [D:\WINDOWS\assembly\GAC_MSIL\NationalInstruments.Common\8.0.20.270__4544464cdeaab541\NationalInstruments.Common.dll] to Version "8.0.20.274" [D:\Program Files\National Instruments\MeasurementStudioVS2005\DotNET\Assemblies\Current\NationalInstruments.Common.dll] to solve conflict and get rid of warning.
2>Compiling...
3>D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3247: Found conflicts between different versions of the same dependent assembly.
3>D:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin\LC.exe /target:LMIO.exe /complist:Properties\licenses.licx /outdir:obj\Debug\ /i:"D:\Program Files\National Instruments\MeasurementStudioVS2005\DotNET\Assemblies\Current\NationalInstruments.Analysis.Enterprise.dll" /i:"D:\Program Files\National Instruments\MeasurementStudioVS2005\DotNET\Assemblies\Current\NationalInstruments.Common.dll" /i:"D:\Program Files\National Instruments\MeasurementStudioVS2005\DotNET\Assemblies\Current\NationalInstruments.DAQmx.dll" /i:D:\Source\OptiGauge.NET\OptiGaugeCommon\bin\Debug\OptiGaugeCommon.dll /i:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Configuration.Install.dll /i:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /i:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll /i:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Management.dll /i:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Runtime.Remoting.dll /i:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.ServiceProcess.dll /i:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /i:D:\WINDOWS\assembly\GAC_MSIL\NationalInstruments.Common\8.0.20.270__4544464cdeaab541\NationalInstruments.Common.dll /i:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.dll /i:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.VisualC.dll /i:D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll
---End Include

I've seen this kind of warning before. Is this a problem? If so, is there a fix for it?

Thanks.

Best Regards,
Matthew

[~jiggawax~]

Did you try and reference the old one again?  The different versions are here: C:\Program Files\National Instruments\MeasurementStudioVS2005\DotNET\Assemblies

Regards,

[MatthewZ]

To be honest with you, I did not try referencing the older version. Doing so would require that I reference the old assembly in a configuration file for projects that use the NI analysis functions. I really do not like the idea of having project specific configurations for assemblies as that becomes difficult to manage.

Also, "reverting" to the old assembly system-wide would is something that I would not think would be a good idea. I assume that NI engineers released a new version of the NI common assembly for a reason, and I would not be surprised if going back to the older common assembly on a system-wide basis causes problems with the newest code.

At this time, the issue does not appear to be causing any problems at run time. If something does go wrong in the future, I'll deal with it then.

I posted partly because the issue was not covered in the release notes for the 8.3 DAQmx drivers when I felt that it was at least worthy of mention in release notes. I did not know if the issue was a.) known, and b.) if it was known, whether it was something to be concerned about or something that was known to cause problems.


Best Regards,
Matthew

Message Edited by MatthewZ on 09-29-2006 12:21 PM

[bilalD]

Hello

This is a known issue that is specific to VS2005.

See this link for more information.

The KB talks about Measurement Studio but the reason is the same. We use policy files to ensure the correct version of Common is being used at runtime and VS2005 seems to display a warning for this. This did not occur with VS2003.

It is safe to ignore this error. You can generate an app.config file to stop the message from occuring, but you will need to make sure you update the config file to take into account the new version of common if you upgrade DAQmx. The app.config file essentially bypasses the policy file.

Policy files are a standard .NET mechanism for ensuring the ensure correct runtime dependencies.

[MatthewZ]

Thank you for the reply. It is always good to know that something like this can be safely ignored.

Best Regards,
Matthew