Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

How to resolve missing NI...WindowsForms assembly in my project after Release deployment.

I built my NetFrameworks project from a VS2005 and Measurement Studio812 platform hosted by wXP and generated a Release compilation.  The project uses MultifunctionDAQ hardware.  I copied the Release compilation over to another box (xp computer) and the project doesn't run; the error msg states an Measurement Studio 8.1.2 assembly can't be found.  I know that the NI dll files (v812) are in the said Release compilation so what's the problem?  Do i need a path statement?  Also, i know that MS81 is installed on the target box; do i need to uninstall v81 or upgrade that to 812?  In the end, I'll need to uninstall MS from the box of the Release deployment.
0 Kudos
Message 1 of 5
(3,168 Views)

Hi,

 

Do you need create a project type setup and deployment using the setup wizard inside of the youir solution. This project will detect all dependencies from the project include the NI merge modules.

 

Regards,

 

Alexandre A.

0 Kudos
Message 2 of 5
(3,163 Views)
The Release compilation runs fine on the development machine.  I have a shortcut that invokes the executable of this compilation and the project runs fine when i start it that way.  The target box that will get the distribution of the final Release currently has an older version of MS installed on it (v8.1).  It's my intention to uninstall all development software from the target box; i.e. VS2005 & MS8.1, and only copy the distribution of my Release compilation over to the target box and run it like it runs on the development box (as aforementioned above).   I already tried to run it on the target box as said on my original post and the error surfaces.  I'd like to minimize installing/uninstalling these huge time consuming development environments (i.e. VS/MS) so that's y i'm posting the question/issue.   What is my minimum effort to have this distribution run on the target box?
0 Kudos
Message 3 of 5
(3,160 Views)

Having read your posting again, i decided to go back into the Project's Properties and see what kind of setting could impact this; so maybe your advise will help.  However, i noticed another problem while playing with this: I get the same error when i try to debug the solution on the target box.  So now i suspect that i have to go 1 of 2 ways; either i:

 

Upgrade my development software as is currently installed on the customer's box, get things running there as they do on my development workstation.  Then when done with that, remove the development software from the customer's box. (and hopefully the Release will still run.)

 

or i:

 

Setup the project properties as u'v said on my development workstation, recompile a Release distribution thereof, remove all development software from the customer's box, and then install the distribution Release on the customer's box (and hopefully it will run).

 

Can i get your comments on this ?

 

 

0 Kudos
Message 4 of 5
(3,154 Views)

Hi Glenn,

 

As we discussed when you called in for support, I think the best route would be to create a Visual Studio Installer by adding a Setup Project to your Solution. This should automatically detect any dependencies and include them in the created installer. 

Manooch H.
National Instruments
0 Kudos
Message 5 of 5
(3,129 Views)