Got 1 MSP which updates all 3 previous versions using 2 Patch Family
elements in my Patch Creation XML. It means having to create a hacked
version of the 1.3 installer which has it's Product Code set to the same
as v1.0 & v.1.1 (and a new Package Code generated) to use in the first
Patch Family Element but it's adding the new files to all 3 older
versions happily. Not quite what I'd like as I've still got 2 different
product codes (upgrade code is the same on all 4 packages thankfully) so
I'll have to use the same method in the future if there are further
similar updates required but it'll have to do.

Moral of the story, be absolutely certain when you're changing Product
Codes (still can't believe I made such an error, hoist by ones own
petard).

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the <Virtual Environment>**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer

 
 

-----Original Message-----
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: 03 March 2010 11:13
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Creating a Major Upgrade Patch

Hi,
I've unfortunately made a bad decision a few months ago which is the
cause of this query.
We have an installer which we've released 3 versions of in the past. All
cosmetic changes to UI etc, components were unchanged between all 3
versions.
V1.0 & v1.1 have product code A.
I (stupidly) released v1.2 with product code B. This works as a major
upgrade to v1.0 or v1.1 quite happily however since it's cosmetic
changes to a 400 MB MSI the majority of our users won't have bothered
with updating since the actual content is no different. Don't ask why I
changed the Product code as I really couldn't tell you what I was
thinking then & I really wish I hadn't now.

I now need to create v1.3 which has a new component with 2 new files in
it. I have created an MSP which targets v1.2 as a minor update as I
haven't changed the product code between v1.2 & v1.3.
I would ideally like to create an MSP which targets all 3 earlier
releases but this doesn't seem possible. I'd be happy to create 2 (or
even 3) separate MSP's & bootstrap them together so the correct one runs
on the users system. The problem appears to be that creating Major
Upgrade patches is as far as I've found, impossible.
MSDN says they're possible
(http://msdn.microsoft.com/en-us/library/aa370579.aspx &
http://msdn.microsoft.com/en-us/library/aa367571.aspx).
However the WiX documentation says they cause problems & aren't
supported ->
http://wix.sourceforge.net/manual-wix3/patch_restrictions.htm
which is backed up by Heath Stewart's blog post ->
http://blogs.msdn.com/heaths/archive/2005/08/22/454552.aspx

Has anyone created & deployed a Major Upgrade patch since the advent of
Windows Installer 3.0?

If it helps I'm using the msimsp/patchwiz method of creating patches but
am not averse to going the WiX/pyro route if needs be. The v1.2 -> v1.3
MSP I've created is 185 kB which updates a 410 MB MSI so you can see why
I would like to create MSP's rather than forcing users to download &
upgrade using the full MSI.

Thanks,

Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501 

http://www.iesve.com
**Design, Simulate + Innovate with the <Virtual Environment>**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP Email Disclaimer

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to