That's not a differential patch. Its a minor upgrade using the msi...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Patches-and-using-instead-of-Component-Guids-tp7594909p7594962.html
Sent from the wix-users mailing list archive at Nabble.co
http://www.firegiant.com/
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Thursday, May 29, 2014 1:29 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using '*' in Component Guids and Patches
You can add the new file in a new location in
://petermarcu.blogspot.co.uk/2009/05/wix-removing-files-with-patches.html
A major upgrade is much simpler.
Dave
-Original Message-
From: Farrukhw [mailto:farru...@gmail.com]
Sent: 29 May 2014 05:16
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using '*' in Component
It might not be a common practice, but I faced it due to some customer
requirement when we have to move a dll to another location. So ethically,
it should be a Major Upgrade which would handle it with no problem. But I
was asked to build a patch, as it is just one dll,
So we build a new dll with a
You should change the component code if the destination of the component
changes, as documented here:
http://msdn.microsoft.com/en-us/library/aa367849(v=vs.85).aspx
Changing the component code is incompatible with minor/small updates; since
you're talking about a patch and a major upgrade patch is
IIRC, I don't think that's going to work out well. You can try but I think
patching across directory moves probably doesn't work out great since IIRC
moving Component directories during repair doesn't tend to work out real well
either. But that's just from memory...
6 matches
Mail list logo
