Recreating a build environment?

[Daklu]

I have a previously released application (v1.1) built using LV2009.  For v1.2 I have upgraded to LV2012 and am using the most recent drivers.  Ultimately I'm trying to allow users to install v1.1 and v1.2 side-by-side, and part of that is recreating the build environment to minimize the impact to the end user's system.

 

I've saved the information in the notification dialog the NI installer displays.  When I install v1.1 on a fresh pc I get this:

Adding or Changing
NI Vision Run-Time Engine 2010 SP1
ActiveX Support
NI-IMAQ 4.6.4
<MyApplicationName> Files
NI-Motion 8.3
Documentation
NI 73xx Controller Support
NI Measurement & Automation Explorer 5.0
NI System Configuration 5.0.0

 

When I install v1.2 on a system with v1.1 already present, I get this:

Upgrading
WARNING: National Instruments system components will no longer be available
NI Vision Run-Time Engine 2012
ActiveX Support
NI-IMAQ 4.7
WARNING: Vision-RIO Support will no longer be available
LabVIEW Real-Time Support
LabVIEW Real-Time 2012 Support will not be available
NI-Motion 8.4
Documentation
NI 73xx Controller Support
NI Measurement & Automation Explorer 5.3.1

 

Adding or Changing
NI Vision Run-Time Engine 2012
.NET Languages Support
NI-Serial 3.8.2 for LabVIEW Real-Time
NI-Serial 3.8.1
NI-Motion 8.4
Microsoft Visual C Support
NI-VISA 5.2
Run Time Support
Configuration Support
Development Support
Real-Time Support
NI I/O Trace 3.0.2
NI System Configuration 5.3.0

 

Removing
National Instruments system components

 

Does anyone have tips for figuring out exactly what drivers are installed with v1.1?  You'd think it would be a simple matter of finding the extra drivers and uninstalling them, but it doesn't seem to be that easy.  The drivers have a lot of dependencies on each other and I cannot, for example, remove NI-Serial 3.8.1.

[JamesMc86]

If I understand correctly you just need driver versions from that system?

Easiest thing is to generate a MAX report (File>>Create Report). This will include a list of driver versions, I'd just go for the standard technical support report.

 

Cheers,

James

[Daklu]

Thanks James, that helped a lot. 

 

I meant to ask for tips figuring out exactly which add-ons or modules were installed when the application was built, not just which drivers were installed by the installer.  Nonetheless, your tip got me going in the right direction and saved me bunches of time.