10-11-2013 05:43 AM
Sorry.. some more info. A DAQmx 9.7.5 installation did not help in the new clean target computer.
I made a temporary solution by installing to our customers the both 190 and 188 until this is solved.. 😉
BR,
Ilkka
PS: If somebody has time at NI, I can always make my computer visible to your engineers by using TeamViewer..
10-11-2013 10:22 AM
Hi,
The runtime error of the target PC is in the attached file..
BR,
Ilkka
10-11-2013 02:47 PM
Can you post a list of your references in your project?
Also, can you just try running a built in example to see if that works?
10-11-2013 04:21 PM
Hi Jesse,
Now I reproduced the problem by using NI examples. I was using the following solution:
C:\Users\Public\Documents\National Instruments\MStudioVS2012\DotNET\Examples\Application\Deployment\WiX\All Libraries\All Libraries.2012.sln
I build it as "x86/Release" configuration and run the Setup.msi in my development computer and in another machine. And I had exactly the same result.. Everything is OK on the development machine but in the other PC the 188 is missing.. Maybe you can make the same there? This is the error in the other computer:
Could not load file or assembly 'NationalInstruments.Common, Version=13.0.40.188, Culture=neutral, PublicKeyToken=dc6ad606294fc298' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
BR,
Ilkka
10-26-2013 01:07 PM
Jesse,
I have been reading this thread with interest because we are experiencing almost exactly the same problem here.
Libraries in use:
13.0.40.190 NationalInstruments.Common.dll
13.0.40.242 NationalInstruments.UI.WIndowsForms.dll
13.0.40.242 NationalInstruments.UI.dll
We also use the following libraries, but have stripped them out to simplify testing solutions to this problem:
13.0.40.167 NationalInstruments.VisaNS.dll
13.0.40.190 NationalInstruments.NiLmClientDLL.dll
No dotfuscator.
One developer's machiine had Common version 13.0.40.188 in the GAC, since removed. Other developers did not have 188 at all.
Code works fine from both Visual Studio and the "installed" version on the developers' machines. It complaines that Common version 188 is missing on machines on which the application is installed that do not have Measurement Studio.
I believe we have tested all combinations of 32-bit and 64-bit developer and end-user instalaltion machines with the same results.
Respectfully,
--Wayne
10-28-2013 11:37 AM
HI WCannon,
I understand that this is a similar issue, but please create a new forum post, because Yltsa's issue hasn't been resolved yet. You can reference this forum post on your new post. Thank you, this is so that we can help both of you the best.
Hi Yltsa,
So based on my understanding, your code works fine in the develpment computer, and not in the target computer correct? Have you looked at this KB ?
Also in here Case 2: 188 is in GAC, you are saying that this is a solution, but you can't use it for other computer, is it because you don't need to install DAQmx 9.7.5?
10-28-2013 12:50 PM
Hi,
Nice to see some activity here.
Please note that 188 is not in the development computer's GAC. And it does not need to be in the target PC's after I install DAQmx 9.7.5.
The problem is that we do not want to instal DAQmx into all target computers. But the missing 188 error is launced always when the program calls NI UI Forms components which should work without DAQmx.
I did not find any useful info from the KB..
Please note that I have opened here also a new thread where I demonstrate the same thing just by using NI WiX deployment example program.
http://forums.ni.com/t5/Measurement-Studio-for-NET/Missing-assembly-NationalInstruments-Common-Versi...
So I think that the problem is not in my code.
BR,
Ilkka
10-29-2013 01:16 PM
What DAQmx is doing chaging/providing the version that is needed. Can you go into all of the assemblies that you have included in your project, and make sure they are all the latest version (same as 190). It could be that some of them are not, and that is why it is looking for 188. Also might be some of the functions that you are using needs 188 version. Can you post your code here, or tell us what assemblies you have with what versions in the references tab in the solution explorer.
10-29-2013 04:46 PM - edited 10-29-2013 04:51 PM
Hi,
please.. the situation is as follows..
I cannot explain this more.. And I think that I am not alone.. there was a similar issue in another NI user..?
Have a nice day 😉
Ilkka
10-30-2013 06:28 PM
That is a very strange behaviour.
We might need to uninstall/reinstall MStudio.
Also try to create a distribution file from one of our examples that contains NationalInstruments.Common and let us know if you get the same error.
Also can you try to create another setup project and make sure in the publish tab under the Application files the ni files were all selected as Include. This has fixed the issue in the past.
There is also a CAR filed on this error: CAR# 161700