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   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Wouldn't AppSearch be enuf?
Answered 05/20/2008 by: AngelD
Red Belt

Please log in to comment
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
Answered 05/20/2008 by: VikingLoki
Second Degree Brown Belt

Please log in to comment