Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

Concurrent installation of Measurement Studio 2008/2015 and Merge Modules result in setup project surprises

We've got enterprise licenses for Measurement Studio 2008 through 2015.  We're still using 2008 and in an effort to migrate our products to later versions of the .net framework so that these applications will function on Windows 10, we've installed both 2008 and 2015 so we may migrate, yet still support builds in the older version for clients under contract.

 

A new version of our product is ready and the pre-existing Visual Studio 2008 setup project was used to build a new installer for this release. The project has not been upgraded to the new measurement studio, yet retains detected dependencies to various merge modules that appear to install DLLs to the path "C:\Program Files (x86)\National Instruments\Shared\".

 

I notice that most of the merge modules are named after their respective measurement studio versions, for example "MStudioUIWinForms.2008.msm" contains libraries for the windows forms implementation of Measurement Studio 2008.

However, three of these merge modules are not labeled as such and only contain the latest version. See merge module "nianalys.msm", which contains the enterprise analysis libraries for the latest version and only the latest version. When the new installation is creating using Visual Studio 2008 (measurement studio 2008), it includes libraries for measurement studio 2015!

 

These libraries require VCRUNTIME140.dll which is part of the Visual Studio 2015 C++ redistributable package.  We are extremely fortunate that this can be installed on windows XP, service pack 3, otherwise we would be forced to have a separate machine that specifically uses 2008.  

 

I bring this up because a new version of Measurement Studio is said to be released sometime this year. If this requires 2017 VC++ libraries XP will not support this and older versions of Measurement Studio will not be functional.

 

Is this a known issue so it may be addressed in future releases? We've elected to simply exclude all merge modules from this point forward in favor of specifying these libraries ourselves to prevent these types of issues from occurring as this sort of thing is the danger of merge modules.  Due to this issue it appears to be dangerous to install two versions of this product concurrently.

0 Kudos
Message 1 of 1
(1,948 Views)