Thanks for the feedback Phil. Do you have any examples of adding vc_redist.exe to a Wix install script?
Thanks, Jeff > The issue has to do with lots and lots of stuff going on when the C++ > runtime support merge modules are uninstalled. I am not aware of any way > to stop them, other than by using the vc_redist.exe package as a > prerequisite install up front and forgetting about merge modules. > > Phil Wilson > > > -----Original Message----- > From: s...@pacaccess.com [mailto:s...@pacaccess.com] > Sent: Wednesday, March 17, 2010 11:33 AM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Uninstalling with merge module now takes nearly three > minutes > > My installer is fairly simple and only installs two files. I just added > the VC8 runtime merge module to my installer. Installation time increased > a little, but the time to uninstall increased a lot. Towards the end of > the uninstall, the uninstaller appears to wait for 2:45 and gives the > appearance that it has hung. I know it hasn't because I'm monitoring the > task manager and I see msiexec churning, but my average user won't know > this and will think it has locked up. > > My application which I'm distributing is built with C/C++ and I am > including the VC runtime merge module in my installer. When I uninstall, > the uninstaller gets half way through, with the message "Please wait while > the Setup Wizard removes My Product", and sits there for almost three > minutes. > > My first question is, is this a known/expected issue? Is there a > workaround? > > > I ran the uninstaller with the following: > MyInstaller.msi /l* output.txt > > > I'm new to Wix, so my second question is, is this the way to debug the > installer/uninstaller, or is there a more verbose method? > > > > While the uninstaller was churning, I opened up the log file and the last > logs were: > . > . > . > RollbackCleanup: File: C:\Config.Msi\d8a95f3.rbf > Action ended 11:15:17: InstallFinalize. Return value 1. > Action 11:15:17: SxsUninstallCA. > Action start 11:15:17: SxsUninstallCA. > 1: sxsdelca tried opening key w/o wow64key 2: > Software\Microsoft\Windows\CurrentVersion\SideBySide\PatchedComponents 3: > 368 4: 0 > 1: sxsdelca tried opening wow64key 2: > Software\Microsoft\Windows\CurrentVersion\SideBySide\PatchedComponents 3: > 392 4: 0 > 1: sxsdelca 2: traceop 3: 1158 4: 0 > 1: sxsdelca 2: traceop 3: 1186 4: 0 > 1: sxsdelca 2: traceop 3: 732 4: 0 > 1: sxsdelca 2: traceop 3: 748 4: 0 > 1: scavenge 2: {5FD88490-011C-4DF1-B886-F298D955171B} 3: > {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4: > {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1 > 1: sxsdelca 2: traceop 3: 748 4: 0 > 1: scavenge 2: {0CA21011-069B-B16A-A5CA-9ABE49DAC05C} 3: > {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4: > {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1 > 1: sxsdelca 2: traceop 3: 748 4: 0 > 1: scavenge 2: {237CD223-1B9D-47E8-A76C-E478B83CCEA2} 3: > {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4: > {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1 > 1: sxsdelca 2: traceop 3: 748 4: 0 > 1: scavenge 2: {13D502A3-FCDA-4843-AA66-CC11FDD94047} 3: > {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4: > {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1 > 1: sxsdelca 2: traceop 3: 748 4: 0 > 1: scavenge 2: {87441A59-5E64-4096-A170-14EFE67200C3} 3: > {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4: > {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1 > 1: sxsdelca 2: traceop 3: 748 4: 0 > 1: scavenge 2: {CAE7D1D9-3794-4169-B4DD-964ADBC534EE} 3: > {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4: > {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1 > 1: sxsdelca 2: traceop 3: 748 4: 0 > 1: scavenge 2: {41A2736B-89A2-40BC-AD98-CC81C375D358} 3: > {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4: > {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1 > > ...which doesn't do me much good (those aren't my GUIDs). > > > > > Maybe the issue has to do with my installer file. Here's what I currently > have: > <?xml version="1.0" encoding="UTF-8"?> > <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";> > <Product > Name="...the name..." > Version="1.1.0.0" > Language="1033" > Id="...guid..." > UpgradeCode="...giud..." > > > <Package > Description="...description..." > InstallerVersion="300" > Compressed="yes" > /> > <Media Id="1" Cabinet="VCCRT.cab" EmbedCab="yes" /> > <Media Id="2" Cabinet="media2.cab" EmbedCab="yes" /> > > <!--BEGIN Test for IE running--> > <InstallUISequence> > <Custom Action="Action1_CheckIfAppIsRunning" Sequence="1" /> > </InstallUISequence> > <Binary Id="Action1_CheckIfAppIsRunning_File" > SourceFile="MyCustomAction.CA.dll" /> > > <CustomAction > Id="Action1_CheckIfAppIsRunning" > BinaryKey="Action1_CheckIfAppIsRunning_File" > DllEntry="CheckIfAppIsRunning" > Impersonate="yes" > Execute="immediate" > Return="check" > /> > <!--END Test for IE running--> > > > <Directory Id="TARGETDIR" Name="SourceDir"> > <Merge > Id="CRT" > Language="0" > SourceFile="C:\Program Files\Common Files\Merge > Modules\Microsoft_VC80_CRT_x86.msm" > DiskId="1" > /> > > <Directory Id="ProgramFilesFolder"> > <Directory Id="INSTALLLOCATION" Name="IE Session Manager"> > <!-- > Component.Guid always remains the same > --> > <Component Id="ProductComponent" Guid="...guid..."> > <File > DiskId="2" > Id="MyDll.dll" > Source="MyDll.dll" > > > </File> > <File > DiskId="2" > Id="MyHelpFile.chm" > Source="MyHelpFile.chm" > > > </File> > </Component> > </Directory> > </Directory> > > </Directory> > > <Feature Id="ProductFeature" Title="ProductComponentTitle" Level="1"> > <MergeRef Id="CRT" /> > <ComponentRef Id="ProductComponent" /> > </Feature> > > <Property Id="WIXUI_INSTALLDIR" Value="INSTALLLOCATION"> > </Property> > > <UIRef Id="WixUI_InstallDir" /> > > <!-- > Upgrade.Id needs to match Product.UpgradeCode above > --> > <Upgrade Id="...guid..."> > <UpgradeVersion > Minimum="1.0.0" > Maximum="1.1.0" > IncludeMinimum="yes" > Property="OLDERVERSIONBEINGUPGRADED" > /> > </Upgrade> > > <InstallExecuteSequence> > <RemoveExistingProducts After="InstallInitialize" /> > </InstallExecuteSequence> > </Product> > </Wix> > > > > Is there anything glaring wrong? Did I mess up the VC runtime merge > module? > > Sorry for the really long message... I didn't know how else to describe > the issue. > > Jeff > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > *** Confidentiality Notice: This e-mail, including any associated or > attached files, is intended solely for the individual or entity to which > it is addressed. This e-mail is confidential and may well also be legally > privileged. If you have received it in error, you are on notice of its > status. Please notify the sender immediately by reply e-mail and then > delete this message from your system. Please do not copy it or use it for > any purposes, or disclose its contents to any other person. This email > comes from a division of the Invensys Group, owned by Invensys plc, which > is a company registered in England and Wales with its registered office at > Portland House, Bressenden Place, London, SW1E 5BF (Registered number > 166023). For a list of European legal entities within the Invensys Group, > please go to > http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. > You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail > inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may > be subject to the terms of any agreements between Invensys (and/or its > subsidiaries and affiliates) and the recipient (and/or its subsidiaries > and affiliates). > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
