File or assembly NationalInstruments.DAQmx was not found...

[RedRhino]

OK, finally I managed to re-install the NI-DAQ Software.

I had to change my "pictures" path to a local directory instead of a network directory... Strange, but now it works again.

Unfortunately my problem was not solved by re-installing the software - the problem remains unchanged.

First of all thank you for the suggestions (and by the way: I hope you had a fantastic christmas time)

I tried to follow your suggestions but I did not understand all of them. I replaced the NationalInstruments.DAQmx.dll (9.2.35.32) with the one I found in the Assemblies (64 bit) - directory which is version 9.4.35.50. When I did, so I got the message (before starting the program) that I have a reference to different versions of NationalInstruments.Common in my project (direct to 8.9.35.302 and indirect to 9.1.35.159) and I should change both to 9.1.35.159.

There is no NationalInstruments.Common.dll in the 64bit assemblies directory so I took the requested dll from the 32 bit directory. I changed the references in my project and then it run, but there was still a warning that the dll was targeting another processor than my project.

I had no idea what that means but when I replaced the 64bit-NationalInstruments.DAQmx.dll with the 32 bit version the project run without warning. The good thing is, that it also runs on a 32bit system!

Thank you again.

[PeterMartens]

Hello,

I am struggling with a similar problem. I am upgrading my software (a .net 4 based program) to work with a newer DAQmx version. The older version that I used did not run on Windows7-64 and the newer DAQmx 9.x does do that, even when you select the normal (32 bit) version. In other words, you can use the non 64 bit version of DAQmx on a 64 bit system.

However, when I take my software to another system (other than my development system), it does not work: a NI DLL version conflict crashes the software. A simple NI example that I built to test it, simply exits without any warning. BTW: Before being able to build the NI example, I had to set the NationalInstruments.Common.Native reference to use the directory 'C:\Program Files\National Instruments\MeasurementStudioVS2010\DotNET\Assemblies\Current', all examples do not seem to work because of this!

When I reinstall the whole NI software with the '.net 4 language 4 support' checked on the target system, it works again. But actually I don't want my end users to have to select development tools for an end-user product. Anybody know how to make this work?

thanks

Peter

[D_Biel]

I'm not sure if I may be missing part of your question here, but let me verify what I think you are asking first. How do you install the .NET 4.0 language support for DAQmx on the end users system without them needing to know they need to install it?

The most common way that applications using NI .NET class libraries are distributed is through a Visual Studio Setup project. With this method, you will be able to include the DAQmx merge module which contains the "language support" for the driver. Essentially, this will install the necessary assemblies and registry keys for your application to run. If you follow the instructions in the Measurement Studio help (also installed with the DAQmx .NET language support), then Visual Studio should automatically detect and include the correct merge modules in the setup project. However, the merge modules do not include the DAQmx driver itself (the components necessary to communicate with the hardware), they only include the .NET support. You will need to install this separately on the end user system. I always recommend running the driver installer as a post install command.

Alternatively or in addition, you can run the DAQmx driver installer with a spec file. This will allow you to preselect what is installed, and even install it without the installer dialog. More info here: http://digital.ni.com/public.nsf/allkb/C361087EE9F20810862577850073128E?OpenDocument

Did I answer your question?

[PeterMartens]

Yes that was my question.

I managed to create a workaround, for NSIS does not support merge modules. I created a sample application based on the NI examples and added a setup project using http://digital.ni.com/public.nsf/allkb/ED87C183E056CAC386256DF1004E54C6

(I could not access Measurement studio help through the MSVS help system). The msi file that was generated then can be executed in my NSIS setup :

  ExecWait 'msiexec /i "$INSTDIR\drivers\FL_NI_Tester.msi" /qn'

thank you for your help.