Usually, the issue is that the Merge Modules do not have all the necessary actions to correctly install themselves (which is incorrect to the spec). If you're missing actions, you can add them to your package by just adding the action name, like:
<InstallExecuteSequence> <WriteRegistryValues/> </InstallExecuteSequence> and you're package will have what the Merge Module should have added. On Mon, Oct 22, 2012 at 10:00 PM, Ingo Fischer <ingoderfisc...@hotmail.com>wrote: > > Hello, > what is the strategy if a 3rd-party Merge Module does not install > correctly?With 3rd-party I mean, I have the files of the Merge Module, only > the msm file. > In my case, if I put the msm in a VS-Installer made msi, it works.If it is > in a WIX made msi, some dll ( COM ) are not registered right. > I thought about extracting the files of the MM using dark and harvest them > again using heat.But what if the MM has custom actions ? > BR-ingo > > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching http://RobMensching.com LLC ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
