11-07-2008 01:18 PM
11-07-2008 01:37 PM
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.
11-07-2008 02:01 PM
11-07-2008 02:46 PM
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 ?
11-10-2008 10:46 AM
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.