2 replies to this topic

[Rayhawk]

[for a home-made MM].  I need to set the install location for the merge-module at run-time [as determined by the presence/absence of a registry key (path) of another product].

What I did was this:
Set the Merge Module's INSTALLDIR to TARGETDIR [I tried setting it to  .  (even via a property) but ISD7 wouldn't allow it].  Then, in the main project, set the merge module's Properties>General>Destination to [PROPERTYNAME]--corresponding to the property which is determined at run-time for the destination.

Building fails, reporting |"can't merge merge-module blah...."|

If I use a predefined property, it works--unfortunately, that is not an option.

This is VERY important, because we're going to have 47 [home-grown] merge-modules in this release.  And they will all have run-time determined destinations [yes, we are insane].

[jhunt]

Maybe MMs are different but this is how I set the Target dir from an msi.

1. Add custom property APPDIR to property table
2. Add reg search MYREGSEARCH to reglocator table
3. Add APPDIR MYREGSEARCH to Appsearch table
4. Add AppSearch action to Execute and UI sequences, very early on.

Now when install runs the registry entry is in the APPDIR property. In my case the value of the APPDIR is the directory we wish to install to.

Then add Custom Action 51 to CustomAction table
SET_TARG_DIR 51 TARGETDIR [APPDIR]\

Finally add this custom action to the UI and execute sequences, AFTER the appsearch actions runs.

It works for me. Hope that helps.

Justin

[luke_s]

What you can do is create your MM with its default location at what you want.

Then in you Main project, use the directory table, and add and entry called
INSTALL.<PACKAGE CODE oof MM> and give it a global property parent.
eg NEWMMINSTALLDIRECTORY

then you can set the above property to what ever you want and your MM should be installed under that.