03-01-2012 04:37 PM
Solved! Go to Solution.
03-02-2012 03:01 PM
Hello Andrew,
Measurement Studio is an additional toolset for Visual Studio. Measurement Studio will require a working copy of Visual Studio to run. Once you have a running version of your software on the developer’s station using the ability of Visual Studio to create an executable you should be able to create an executable that includes the necessary DLLs and libraries for your application to run.
If you are trying to develop on these additional computers you will need a copy of Visual Studio. When trying to run an executable it should work, if not copy the DLL’s with the file.
Daniel
03-05-2012 12:36 PM
Hi Andrew,
You don't have to install Visual Studio on your target systems to get your DAQmx application to work properly. Once you have built your DAQmx application on your development computer you have two options for deploying which are:
In addition to one of the above options, you must also install the DAQmx driver to get the underlying depenendies on those targets systems. We have topics in our help called "Measurement Studio .NET Merge Modules" and "Measurement Studio .NET XCOPY Deployment Files" that list out all the files you need to deploy.
Measurement Studio Common versioning and deployment is slightly different in that Common uses policy files to redirect applications to the latest Common on the system. This is discussed in the "Measurement Studio .NET Class Library Versioning for Development and Deployment" help topic. I would highly recommend you read that.
In the end, if you are building against 9.1.40.159 of Common, you need to make sure you target systems have at minimum, that version. They can have higher versions as the policy files will take care of that.
Hope this helps.
03-05-2012 12:39 PM
03-05-2012 12:46 PM
Hi Andrew,
You don't have to have Measurement Studio installed on the deployment systems to get your application to work. All required dependencies should be available via merge modules or as standalone files via XCOPY (e.g., unless its specifically called out in the help that the library doesn't support XCOPY deployment).
There isn't a standalone installer for Common that we have available. The suggested approach is that you build a setup project in Visual Studio which will include all required dependencies, include Common. When you run this setup project on your target system it will install your application along with the required dependencies (e.g., DAQmx.dll, Common assemblies, VC runtime dependencies, etc).
03-05-2012 01:02 PM
Thanks for the reply Jonathan. I've tried building an installer package with the required merge modules, but for some reason the common dlls don't end up on the target system, and thus throw exceptions when the runtime tries to load them. I'll try rebuilding the installer and see if that works, thanks for your help. I'll let you know how that goes.
Andrew
03-06-2012 04:23 PM
Your suggestion of rebuilding the installer worked just fine. With the correct merge modules and dependencies detected, the application worked the first time after it was installed.