To get the actions with the standard sequence numbers, you should only need add the standard action element to the sequence by itself.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick Sent: Wednesday, May 23, 2007 11:50 AM To: 'Pseudonymic Wannabe'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] RegisterClassInfo / RegisterProgIdInfo not called? Probably that WiX only includes the minimal set of actions in the execute sequence, where other tools pretty much use the template setup verbatim. The merge modules should really include those actions in their ModuleInstallExecuteSequence. The workaround is to schedule the actions yourself using <InstallExecuteSequence>. According to Sequence.MSI in the 2003 R2 SDK (C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Samples\SysMgmt\Msi\database\Sequence.MSI), these actions should be scheduled as: UnregisterClassInfo 2700 UnregisterProgIdInfo 2900 UnregisterTypeLibraries 2300 RegisterClassInfo 4600 RegisterProgIdInfo 4800 RegisterTypeLibraries 5500 WiX's actions.xml uses the same values (src\wix\Data\actions.xml). -- Mike Dimmick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pseudonymic Wannabe Sent: 23 May 2007 10:45 To: wix-users@lists.sourceforge.net Subject: [WiX-users] RegisterClassInfo / RegisterProgIdInfo not called? Aye more mergemodule stuff. Been trying for the life of me to debug the merge-modules we use here that refuse to work on Win2k in our MSI package. So I ran an old WISE installation we had with the merge-modules in them and after that our application runs, so somehow that did it right. So I grabbed the MSI file from the WISE package and ran it with /lvx to log and I noticed that the Mergemodule components are being called with RegClassInfoRegister and RegProgIdInfoRegister in that installation but not in the new WIX 2.0 one. I'm guessing this could be the reason for the mergemodule components for failing. It jumps straight from CreateShortcuts to WriteRegistryValues when it should preferably have RegisterClassInfo and RegisterProgIdInfo actions in between. Why are those calls not called in our new WIX based MSI package? I thought they were part of the default installexecutesequence. Thanks! _________________________________________________________________ Like the way Microsoft Office Outlook works? Youll love Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migratio n_HM_mini_outlook_0507 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
