This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: MSXML 4.0 merge module deployment issue
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 17, 2008
09:38 AM
MSXML 4.0 merge module deployment issue
Hi Everybody,
When you include the MSXML 4.0 merge module for Windows XP and Later (the one which should be installed in WinSxS),
after a major upgrade when you click on the advertised shortcut
it enters into auto repair mode.It happens only the first time you run application.
Does anyone know if this issue has been fixed ?
Thanks in advance
Romain
When you include the MSXML 4.0 merge module for Windows XP and Later (the one which should be installed in WinSxS),
after a major upgrade when you click on the advertised shortcut
it enters into auto repair mode.It happens only the first time you run application.
Does anyone know if this issue has been fixed ?
Thanks in advance
Romain
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 17, 2008
10:55 AM
This is related to how CostFinalize determines what needs to be installed during the costing process. For .NET assemblies installed to the GAC and Win32 side-by-side assemblies, MSI does not perform the actual installation of these resources, so it "guesses" at what needs to be done with them when they are already on the machine (see http://support.microsoft.com/kb/905238/en-us for a detailed desciption).
You can try resequencing the RemoveExistingProducts action to later in the sequence (you can do this with the "Install setup then remove unneeded files" option in the Upgrades view Upgrade Windows Installer Setup node).
You can try resequencing the RemoveExistingProducts action to later in the sequence (you can do this with the "Install setup then remove unneeded files" option in the Upgrades view Upgrade Windows Installer Setup node).