Dependencies not recognized (dependencies...schmependencies)

[altenbach]

I had LabVIEW 2018 and 2019 installed (+ some kits) and I thought I try to uninstall LabVIEW 2018.

Thinking that NIPM will correctly identify all dependencies, I only selected LabVIEW 2018SP1 to be uninstalled and got a warning of two dependencies that would also get uninstalled. I OK'd them. After all was done, NIPM still showed the presence of at least three 2018 toolkits that have no meaning in the absence of LabVIEW 2018. Why did they not get mentioned or uninstalled as dependencies???

(Here's a section of the "installed" section of NIPM)

My wild guess is that these are not recognized because they are not marked as SP1, but they probably should be included as dependencies, because plain LabVIEW 2018 (non-SP1) and SP1 of the same version cannot really coexist on the same machine (?).

[lincolnlin]

altenbach,

LabVIEW 2019 is the first release that the LabVIEW platform installer is fully converted to NIPM based packages.

The LabVIEW 2018 toolkits were built using our previous installer framework, which does not have the dependency relationship with the LabVIEW core 2018 package. There's only a DistributionLaunchCondition check that LabVIEW Core must be installed before you install the Toolkit, but there's no such check during uninstallation time. (There's some technical limitation on this...)

The issue had been fully addressed in LabVIEW 2019 release.