Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

DAQmx and Common versions

Hi,

I'm wondering if its supposed to work like this:

You compile your code with a specific version off DAQmx and Common, and run on that computer - it works.
If you have another computer with a different version of DAQmx and Common - it does not work.
I mean do you need to have the same version on these two files on all computers where you run with DAQ, and of course compiled with that exact version?

Because I have three different setups and the file I have compiled on one computer does not work on the other two computers and the other way around...

Thank you for your support!


0 Kudos
Message 1 of 2
(3,307 Views)

Hi IsaFisa,

 

Its always best practice to deploy whatever versions of the assemblies you are building against to the end-user system.  The easiest way to take care of this is to build some type of MSI setup project (i.e. if your using VS, then you can use the VS setup projects) that includes the appropriate DAQmx and Common assemblies. This setup project will contain all the needed .NET pieces. Then you must also make sure to install the correct underlying DAQmx driver. So if you are building against version 8.8, then its best to deploy all 8.8 assemblies and underlying components. 

 

If you create a VS setup project and point it to the output of your Windows application, VS should automatically pull in all the needed .NET components.

 

What you are seeing is how .NET works in general. If you are building against version 8.8.xx.xxx, then you *must deploy that version on the target system in a location that the .NET CLR will look. If you don't, then the CLR won't be able to locate that assembly and your application won't work.

  

* You can of course always get around this by using config files or policy files to redirect a version to some other version.

 

I would suggest reading through our Deploying Applications help topics. In particular, take a look at Deploying Windows Applications, .NET Merge Modules, and .NET Class Library Versioning for Development and Deployment.

 

Best Regards,

Jonathan N.
National Instruments
0 Kudos
Message 2 of 2
(3,289 Views)