Re: [WiX-users] ModuleInstallExecuteSequence not being merged into msi
That was in fact the problem, thanks! On Sat, Mar 22, 2008 at 11:42 AM, Bob Arnson <[EMAIL PROTECTED]> wrote: > Geoff Finger wrote: > > In the ModuleInstallExecuteSequence table of the msm files we have rows > such as: > > > > Action: RemoveOldDriver.B391C18A_6953_11D4_82CB_00D0B72E1DB9 > > Sequence: > > BaseAction: CostInitialize > > After: 0 > > Condition: INSTALLCONDITION=1 > > > > Does the ModuleInstallExecuteSequence table in the .msm also have a row > for CostInitialize? Mergemod.dll requires merge modules to be > "self-contained" in how they schedule actions. See the > ModuleInstallExecuteSequence table doc in the MSI SDK for an explanation > -- even if it's a lame one. Try using smoke.exe to run validation on > the merge module; it might provide details about problems that lead to a > fix. > > -- > sig://boB > http://joyofsetup.com/ > > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ModuleInstallExecuteSequence not being merged into msi
Geoff Finger wrote: > In the ModuleInstallExecuteSequence table of the msm files we have rows such > as: > > Action: RemoveOldDriver.B391C18A_6953_11D4_82CB_00D0B72E1DB9 > Sequence: > BaseAction: CostInitialize > After: 0 > Condition: INSTALLCONDITION=1 > Does the ModuleInstallExecuteSequence table in the .msm also have a row for CostInitialize? Mergemod.dll requires merge modules to be "self-contained" in how they schedule actions. See the ModuleInstallExecuteSequence table doc in the MSI SDK for an explanation -- even if it's a lame one. Try using smoke.exe to run validation on the merge module; it might provide details about problems that lead to a fix. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] ModuleInstallExecuteSequence not being merged into msi
I'm having some trouble getting a couple of 3rd party msm files to work correctly. The original instructions said that along with including the merge module we should also schedule several custom actions in the msi. After that failed I looked around the archives and found several threads saying that's not how it's supposed to work and merge modules that require that are badly designed. (Of course I already kind of suspected that when I discovered that all three of the merge modules in the package had identical GUIDs with just one digit switched between each of them =) So we decided to edit the original merge modules with Install Shield and insert the custom actions into the ModuleInstallExecuteSequence tables. However when we rebuilt the msi we found the custom actions still weren't getting called. When I opened the newly built msi with Orca I found that the Custom Actions show up correctly in the CustomAction table, but that no new rows are being merged into InstallExecuteSequence. Is there something special that needs to be done to get that to happen? I didn't see any obvious errors when running the makefile, and I don't see anything about it in the documentation for the merge element. I'm using Wix 2.0 and what I have in the code is elements such as: In the ModuleInstallExecuteSequence table of the msm files we have rows such as: Action: RemoveOldDriver.B391C18A_6953_11D4_82CB_00D0B72E1DB9 Sequence: BaseAction: CostInitialize After: 0 Condition: INSTALLCONDITION=1 I was a bit suspicious of the GUID being tacked on there, but doing it with and without the GUID doesn't seem to make any difference. I was also unsure about leaving the Sequence column blank, but adding a specific sequence number didn't seem to help either. Since I haven't been able to find any threads from other people encountering the issue it seems like it has to be something really simple that I'm missing. Thanks for any help! - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
