Thank you for the response. It is very helpful.
Phill
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-Best-practice-using-fragments-tp7587660p7587722.html
Sent from the wix-users mailing list archive at Nabble.com.
-
he two versions, it
will not be included in the patch (doesn't matter if it was included or not).
-Blair Murri
> From: jocoo...@jackhenry.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 29 Jul 2013 18:41:19 +0000
> Subject: Re: [WiX-users] [Patch] Best practice using f
acob.hoo...@greenheck.com]
Sent: Monday, July 29, 2013 1:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] [Patch] Best practice using fragments
I think the part you are missing is " all changed components from that fragment
will show up in your patch". I
I think your right. I had noticed that phrase, but was not certain of my
interpretation of it. I agree that I don't know why I would ever deploy a
subset of "changed" files in a ComponentGroup. So in that case I guess I am
ready to move on in testing my new setup.
Thanks.
Phil
--
View this me
, July 29, 2013 11:40 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] [Patch] Best practice using fragments
I am relatively new to WiX 3.7 and MSI (and having lots of fun with the great
WiX documentation and information available in the forum). As I get my BA/msi
functional I am t
I am relatively new to WiX 3.7 and MSI (and having lots of fun with the great
WiX documentation and information available in the forum). As I get my
BA/msi functional I am trying to review best practices and I came across a
post at:
http://stackoverflow.com/questions/471424/wix-tricks-and-tips
In
6 matches
Mail list logo
