What release has nationalinstruments.common v 8.1.20.168?

[MatthewZ]

Here's my dilemma.

I recently updated to MS 8.1.1 which apparently uses the assembly NationalInstruments.Common 8.1.20.235. I am also using the assembly NationalInstruments.DAQmx 8.5.20.22 which apparently uses NationalInstruments.Common 8.1.20.168

I am using a document generator to document our code that parses assemblies. When the document generator gets to the NationalInstruments.DAQmx assembly, it quits because it cannot find the assembly NationalInstruments.Common 8.1.20.168. So, I am wondering where I might find a copy of this assembly so that I can use it to satisfy the document generator. We have the MS maintenance plan, so I have several previous releases where I might be able to find the appropriate assembly.

Note, I have remapped the assembly at the machine level and in the app.config file for the project that depends on the DAQmx assembly to direct requests for the 168 version of the assembly to the 235 version of the assembly, however, this does not solve the problem for the document generator.

Thanks in advance!

[drohacek]

Measurement Studio 8.1 shipped version 8.1.20.168. If you installed 8.1.1 on the same machine that has 8.1, you should be able to find 8.1.20.168 in the Global Assembly Cache or in the Program Files\National Instruments\MeasurementStudioVS2005\DotNET\Assemblies\8.1.20.168 directory.

However, I'm not exactly sure why you need this version of the assembly. NationalInstruments.Common.dll uses a policy file to redirect all references to it to the latest version installed on the system. This means that when the .NET Runtime loads NationalInstruments.DAQmx.dll 8.5.20.22, it will load NationalInstruments.Common.dll 8.1.20.235, even though NationalInstruments.DAQmx.dll 8.5.20.22 references NationalInstruments.Common.dll 8.1.20.168.

For more information on this issue, see the help topic titled, "Measurement Studio .NET Class Library Versioning for Development and Deployment", in the NI Measurement Studio Help.

On the other hand, I don't know exactly how your documenter works, so you might need NationalInstruments.Common 8.1.20.168. What documenter are you using?

[gcsd_dano]

I believe that we are seeing the same error using the MicroSoft SandCastle documentation tool.  Although we can build and run our application, the MicroSoft MrefBuilder tool is not redirected to the latest version of the NationalInstruments.Common assembly (8.1.20.237) and insists on version 8.1.20.235 which we do not have.  Has this been verified as a MicroSoft limitation?  Is there a way to obtain the 8.1.20.235 version of the NationalInstruments.Common assembly?

MrefBuilder Error Message:

MrefBuilder (v2.3.8000.26)

Copyright c Microsoft 2006

Info: Loaded 3 assemblies for reflection and 0 dependency assemblies.

Error: Unresolved assembly reference: NationalInstruments.Common (NationalInstru

ments.Common, Version=8.1.20.235, Culture=neutral, PublicKeyToken=4544464cdeaab5

41) required by NationalInstruments.UI

Message Edited by gcsd_dano on 03-17-2008 05:26 PM

[gcsd_dano]

This thread seems to be stating the same problem:

http://forums.ni.com/ni/board/message?board.id=232&message.id=6375&requireLogin=False

[fivealive]

Hello,

   I'm not using the xml tool but I'm loading my functions that use the NI assemblies through reflection.  Anyways we run into the problem that the nationalinstruments.common is not found and their is a later one on my machine due to updates and what have you.  The reason it looks for that particular version is that the NI288.2 references that version.  However this isn't a problem for your compiler as that redirector will use the newest common version and is happy with that.    I guess somehow when doing the reflection the policy needs to be added so things can be figured out.  Not sure... 

   I wonder if they can just have some place to get this assembly as it isn't on my machine.

Thanks

[Steak McDAX]

Hi fivealive,

Currently, we do not have a common place to obtain the older versions of this DLL.  Our Research & Development Department is looking into this issue and deciding what is the best way to make this information available to our users.  Thanks for the feedback!

[calvin ngc]

that was 2008 anything yet ?

[gcsd_dano]

This may be the answer for which we are looking (I haven't tried it though):

http://sandcastle.codeplex.com/discussions/36323?ProjectName=sandcastle