I am not an expert on patching but I would like to mention that normally
MSI's only understand 3 part version numbers. So 2008.0.14.0 and
2008.0.14.30 are seen as the same version by windows installer.
Neil
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nick
Hennemann
Sent: 13 April 2007 14:19
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching, patching, and more patching.....
Hello,
>From research I have done, it appears that this type of question has
been asked a few times before (so please hang in there)...but I am still
a little sketchy on the details of how to accomplish it or maybe if I'm
not understanding the process correctly.
Here is what I would like to do:
* Create the RTM version of my installer
* Be able to patch the RTM version with any patch that I create
for it
* Also be able to patch the RTM version that has already been
patched with a previous (earlier) patch
In other words, if I release version 2008.0.14.0 I would like to be able
to patch it (and all the RTM's with previously distributed patches
applied) with the latest a greatest patch (let's say 2008.0.14.30)
* I would be able to patch 2008.0.14.0 to 2008.0.14.30
* I would be able to patch 2008.0.14.15 to 2008.0.14.30
* Etc, etc, etc
Now, it appears that this can be accomplished by adding <ReplacePatch>
and additional <TargetImage> tags in the patch file. I have attempted
to create this patch and it "seems" to work (although some things
concerned me when looking at the patch.log, but side point anyways). My
real concern is if I want to accomplish this it appears that I would
have to have an "administrative" image of every single patch and then
reference it in my PCP file with a <TargetImage> tage....my
"administrative" images are over 250MB in size and we could easily have
over 50-80 patches created during the time this software would be in use
by our customers.....we are talking 12 - 20 GB of hard drive space (I
know, I know...hard drive space is cheap) and it seems like the patch
creation process would take for ever!!! I tried this with just a few
administrative images and it seems to really take a lot longer than when
I only had 2 administrative images to deal with so I can only image how
long it would take with 50 admin images to deal with. Hopefully, I am
misunderstanding how to create patches that will accomplish my goals
above and there is a cleaner way.
Anyone else out there trying to accomplish the same thing or have
already done so successfully? I would love to have your input.
Thanks,
Nick H.
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively
for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged
information. Any unauthorized review, use, printing, saving, copying,
disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately
advise the sender by reply email and delete all copies.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
