Can I separate the installers for NI dlls and my executable?

[ArnoudC]

Hello,

Is it possible two create two separate installers, one for the NI dlls & ocx, and a second one for our application? We don't want to install & reinstall the NI dlls and change the registry settings every time the application is changed. So the idea is to see the NI dlls & settings as a runtime library, which is never changed. Is this possible? And does the application need to edit the registry?
Also, the standard installer installs mesa.dll in C:/Program Files/National Instruments/Shared/Mesa. Is it possible to install it in a different place? The application directory possibly?

Thanks,
Arnoud Celie

[bilalD]

It really depends on which components your application is using. We do provide merge modules for Measurement Studio .NET and ActiveX components, so you can create installers for them. If you are using NI drivers (DAQmx, VISA etc.)however, you need to use the driver installers themselves, since those installers do alot more than copy dlls.

Mesa does not have to be in the shared location. It can also be in the application's local directory. I tried this out with CVI and the Measurement Studio controls.

In most cases, I find it's a safer bet to deploy the application with the actual components you developed the application with. So combining the app executable and its dlls in one installer is a good way to make sure that the user always has the same components you tested your application with.