Changing the GUID of your component makes no difference to anything in your example. Your code is telling the Windows Installer to uninstall any old version of your software before it installs the current version. If this is the only way your installers will work then your GUIDs can be the same or different regardless. To the best of my knowledge you should not need to care about component GUIDs unless you are planning on patching using MSP's.
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: Lough, Norman [mailto:norman.lo...@imass.co.uk] Sent: 09 March 2009 13:37 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Upgrades The code below clears out previous versions for me. <Product Id="23cc363c-b9d2-451b-a349-38b91bd487c6" Name="Common 1.0.4.0" Language="1033" Version="1.0.4.0" Manufacturer="Company Name" UpgradeCode="9d32a378-0b1e-492a-9a40-dd80deb8ab55"> ... <Property Id="PREVIOUSVERSIONSINSTALLED" Secure="yes" /> <!--The upgrade Id should refer to the Upgrade Code shown under Product--> <Upgrade Id="9d32a378-0b1e-492a-9a40-dd80deb8ab55"> <UpgradeVersion Minimum="1.0.0.0" Maximum="1.0.3.9" Property="PREVIOUSVERSIONSINSTALLED" IncludeMinimum="yes" IncludeMaximum="yes" /> </Upgrade> ... <InstallExecuteSequence> <!--To remove previous versions--> <RemoveExistingProducts Before="InstallInitialize" /> </InstallExecuteSequence> ... I ran a test where I went from Version 1.0.3.0 to 1.0.4.0. In the 1.0.3.0 version the root directory contained 3 files Default.aspx, Web.Config and TextFile1.Txt. In Version 1.0.4.0 I no longer included TextFile1.Txt. The product code changed (I left the upgrade codes as before). I changed the guid for the root directory component to see what would happen when Version 1.0.4.0 was installed over the top of 1.0.3.0. Even though the guid changed the original file TextFile1.Txt no longer remained - I suppose this is to be expected since as far as 1.0.4.0 is concerned TextFile1.Txt is not part of its installation. Could someone explain if there is any significance attached to me changing the guid of the root directory (or any other directory component) in this context. The reason I ask is that I'm looking to automate the wxs file creation based on a periodic publication of a website. It seems from the above that I can just create the guids for these directory components on the fly rather than maintain a record of previous folders/components (some of which may or may not persist)? <DirectoryRef Id="ZTESTWEBSITEDIR" FileSource="C:\Temp\zTestWebSitePublished"> <!--Version 1.0.3.0 090ed5bc-58c3-41fd-90b9-dc769f5e4551--> <!--Version 1.0.4.0 1ba6ce1b-2df1-4894-a4d3-9ec75c68ab44--> <Component Id="zTestWebSiteRoot" Guid="1ba6ce1b-2df1-4894-a4d3-9ec75c68ab44"> <File Id="Default" Name="Default.aspx"></File> <File Id="WebConfig" Name="Web.Config"></File> <!--<File Id="TextFile1.Txt" Name="TextFile1.Txt"></File>--> ... Thanks Norman Lough Developer Tel: +44 (0)191 213 5555 DDI: +44 (0)191 2028360 Email: norman.lo...@imass.co.uk Imass Ltd, Northumbria House, Regent Centre, Gosforth, Newcastle upon Tyne, NE3 3PX. http://www.imass.co.uk <http://www.imass.co.uk/> Imass Limited is an Infoterra company, part of EADS Astrium Registered in England and Wales No. 2379476 - Disclaimer - The information contained in this e-mail and its attachments is confidential and intended only for the use of the individual or entity named above. If you are not the intended recipient, please do not read, copy, use or disclose this message or its attachments. If you have received this message in error, please notify the sender immediately and delete or destroy all copies of this message and attachments in all media. Any views expressed in this e-mail that do not relate to Imass' official business may not reflect the views of the company. ------------------------------------------------------------------------ ------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
