Application installer error with NI System Configuration

[dan_u]

Hardware configuration might be a different issue.  But still I think it should be possible to work with 2 applications that use different driver versions. Just like a compiled LV application uses the right LV Runtime, it should use a compatible driver version.

Essentially what I need is to detect RT systems on the network from my application. I need NI System Configuration for this. I guess the functions I use would work with the newer version (NI System Configuration 5.6 is compatible with LabVIEW 2013/2012/2011/2010). But it does not let me install the application because my installer contains NI System Configuration 5.5.1 (also compatible with LabVIEW 2013/2012/2011/2010).

If it would be the opposite, my installer contains a newer driver version, it would install without notice. This is the same risk of breaking existing applications that use the older version. So IF you want to be on the safe side, the installer should also NOT update a driver to a newer version. Somehow that logic does not sum up IMHO.

[Intaris]

This is crazy behaviour from an installer from a company which releases updated development suites twice a year.

I believe there should be significantly more work done in allowing driver pachages to install in parallel, just like .NET and even the LabVIEW run-time does.

I have an idea on the idea exchange which has very little traction which would solve exactly this problem.

[dan_u]

Well, it seems we cannot expect a solution for this soon.

Is there at least a recommended workaround? Can I tell the client to contact NI to buy him a second PC (according to AQ here)?