/build/static/layout/Breadcrumb_cap_w.png

Detect non-msi application install dir?

I'm packaging a bunch of additional files as an add-on for a 3rd party application that was not installed via Windows Installer. There is no control as to which directory this application can be installed in. The application's root directory can be off of C:\, C:\Program Files, anywhere. I want to have a detect function/custom action to set the INSTALLDIR to where the application was detected as opposed to blindly accepting a user provided INSTALLDIR. There are specific files I can search for and a specific directory structure beneath the install directory, but no registry keys.

Does anyone already have a method of accomplishing this in an MSI before I re-invent the wheel?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: AngelD 16 years ago
Red Belt
0
Wouldn't AppSearch be enuf?
Posted by: VikingLoki 16 years ago
Second Degree Brown Belt
0
Oh, it's that easy? :-P
(I moved on from full-time packaging about 2 years ago... brain is getting dusty)

...Now reading documentation for "AppSearch"
Thanx! lol
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ