I'm curious as to why people encounter issues with this. I've never had to do
anything special for Windows Installer to do this automatically for our
packages. Unfortunately I have run across situations where upgrade or uninstall
of someone else's product prompts Windows Installer to request
I can think of some:
Advertising.
Use of the resolve source action without a condition to prevent it after
first time installation.
Binary delta patching where the original file is not available, perhaps
because it's been overwritten
Since we avoid all of those, we've never had the problem
As mentioned, this is triggered by the Resolve source action and there are
multiple reason why this is needed and there are multiple ways to help reduce
the need.
The largest cause is when uninstalling a patch. I personally use full file
replacement when building patches as it significantly
Dear All,
After installing our product, doing Modify/Repair from the Add Remove
Programs window requires the original install package to be in the same
location where the product is installed from. Does anyone know how to cache msi
locally such that Modify/Repair the product via Add Remove
There is no generic way to do this, You will basically have to write your own
custom actions that does this task and updates the source list for the MSI
package.
I personally created a merge module with a set of actions that cache the MSI in
a set location and handle any cleanup and
Do you have a ResolveSource action in your Sequence tables ? If so, search on
this list for resolveSource for some ideas about how to handle it.
-Original Message-
From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com]
Sent: 17 May 2011 16:44
To: General discussion for Windows Installer
Hi Mat,
Thanks a lot for the very useful information. If you can, please also share
with us your merge module code.
Thank you,
Miaohsi
-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Tuesday, May 17, 2011 8:58 AM
To: General discussion for Windows
7 matches
Mail list logo
