Identifying installation destination

[Oli_Wachno]

Hi!

Is there a way of identifying installaton destination using NIPM after the package has been installed? Say.... I want to know where a certain package has been installed to?

Cheers

Oli

[Scott_Richardson]

Oli, a package can specify files that install to many location. More specifically, a file in a File package specifies any of the target roots supported. A file in an WinInst package is installed by an MSI. Many of the target roots are what NI calls NIPaths which correspond to locations specified by registry keys. NIPM tracks whether a package is installed. NIPM does track in a database both the WinInst and File packages that have been installed, and where files from File packages were installed so that they can be uninstalled when required, but that information is not exposed to end-users via any API. NIPM relies on the MSI Engine and its caching to know where WinInst files were installed.

Can you give more details about what you are trying to do?

[Oli_Wachno]

Hi Scott,

in this particular case, I am trying to find out, where the LabVIEW Runtime Engines are installed to.

Cheers

Oli

[WesW · Accepted solution]

You can use these registry keys to determine this (and parallel registry keys in the 64-bit registry for the 64-bit run-time):