Hi Bob, The problem is that the exe that I am referencing is actually in the MSI that I am merging into. Basically the MSM just contains a bunch of static registry entries (i.e. basically just adding the registry keys for the exe's type library information). If I just [#blah.exe] in the MSM, it still appends the guid which doesn't map to [#blah.exe] in the MSI.
The reason its an MSM is because these registry keys are merged into all the different products that contain the blah.exe file. Maybe the way things are setup now isn't the best way. I'd be happy to restructure if that was the better solution. Thanks -- View this message in context: http://n2.nabble.com/Using-INSTALLDIR-in-MSM-That-Eventually-Reflects-the-MSIs-INSTALLDIR-tp2935794p2943957.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
