Creating an MSI that just replaced that file with a higher version will work as 
long as the component guid is the same. Visual Studio setups don't expose 
Component guids, so I'd guess that the component guids are not the same, that 
would explain it. 

Phil Wilson 

-----Original Message-----
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] 
Sent: Wednesday, July 13, 2011 1:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating a "hotfix" patch for an installer built with 
VS

By the sound of it you created an MSI that contains only your hotfixed file ?
That would explain the behaviour you're seeing.

You could make:
Major upgrade
Hotfix patch
There's a minor update but it probably won't give you any advantages over a
major upgrade.

The easiest, if you have the original installer's source code, is to make a
Major upgrade. A major upgrade automatically removes the old version and
replaces it with the new one. However when you remove the new version, the
old version isn't reinstalled.

If you want a small update patch (.msp), this is more difficult to write and
requires that the Windows Installer rules are followed more closely in the
original and new installers. The patch can be removed to get back to the
original installation state.

There are some rules you have to follow for the different update types which
are documented in the MSDN
http://msdn.microsoft.com/en-us/library/aa370579%28v=VS.85%29.aspx
If you're making a major upgrade then you can have Wix write the upgrade
table entries for you using the MajorUpgrade 
element.

1. Yes you can with the Permanent attribute but it would be a bad way to fix
your problem.
2. If you create one of the two update types, the files will all uninstall
correctly.

-----Original Message-----
From: Ben Peikes [mailto:bpei...@gargoylestrategic.com] 
Sent: 12 July 2011 18:42
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating a "hotfix" patch for an installer built with VS

We have an old project whose installer was built using VS. I need to
replace one of the files, so I want to create an installer with WIX
which just installs a single file. The "hotfix" installer I've created
works fine when installed, but when it gets uninstalled, it removes the
file. I'd like it to replace the file that it updated when uninstalled
with the original, but I'm not sure how to accomplish that.

 

A couple of questions:

1)      Is there any way to mark a <File> or <Component> such that it
does not get uninstalled when you uninstall the product?

2)      Is there a way to tie my wxs to another product and version
such that if the other product gets uninstalled, the hotfix
automatically gets uninstalled as well?

 

 

-----------------------------------------------------------------------------
-
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on "Lean Startup 
Secrets Revealed." This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.


------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on "Lean Startup 
Secrets Revealed." This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 
7AW (Registered number 166023). For a list of European legal entities within 
the Invensys Group, please go to 
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail 
recept...@invensys.com. This e-mail and any attachments thereto may be subject 
to the terms of any agreements between Invensys (and/or its subsidiaries and 
affiliates) and the recipient (and/or its subsidiaries and affiliates).



------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on "Lean Startup 
Secrets Revealed." This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to