Reading the tutorial at http://www.tramontana.co.hu/wix/lesson4.php once again, I'm even more confused: "You have to [do a major upgrade] when you change the name of the .msi file for any reason.". But who on earth would distribute a small update to an existing product with the same .msi file name?!? Especially as a small update is considered to only replace a few files. And what if the user decides to rename that file?
I _assume_ that what I am trying to do is exactly the above: a small update (don't want to uninstall) with changing file names (featuring the date of the build or build number). Is this really not possible? Michael Am 16.02.2009, 19:59 Uhr, schrieb Alexander Shevchuk <alexander.shevc...@microsoft.com>: > Hi Michael, > > Make sure you follow all required steps to make major upgrade work. In your > simplified code I see Version attribute hard coded to "0.0.0.0". Also, you > did not provide your <Upgrade> table and how you schedule > <RemoveExistingProducts>. It is not obvious from your code if you change > Product/@Id with every build. > > Regards, > > Alex > > > > -----Original Message----- > From: Michael Herger [mailto:s...@herger.net] > Sent: Monday, February 16, 2009 7:00 AM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Updating full package > > Hi! > > I'm working on a Windows Home Server add-in. This is not intended for > production systems yet. We're publishing nightly builds and want users to be > able to just install on top of what they had before. > > The problem I've encountered is that either the packages install as different > applications, leaving a mess with daily installations (of which only one can > be uninstalled), or that I can't install one file on top of the other without > uninstalling the old version first. I've been following several postings, > tutorials etc. (eg. > http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx), > but to no avail. > > Here's my simplified code: > > <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";> > <Product > Name="MyApp for Windows Home Server" > Id="xxxxxx-f914-11dd-87af-0800200c9a66" > UpgradeCode="xxxxxxx-EBBC-11DD-BA2F-0800200C9A66" > Manufacturer="Me" > Version="0.0.0.0" > Language="1033"> > > <Package > Manufacturer="Me" > InstallerVersion="200" > Languages="1033" > Compressed="yes" > Id="*" > /> > > <Media Id="1" Cabinet="MyApp_0.0.0.0.cab" EmbedCab="yes" /> > > <Property Id="WHSLogo">1</Property> > > <Directory Id="TARGETDIR" Name="SourceDir"> > <Directory Id="ProgramFilesFolder"> > <Directory Id="WHS" Name="Windows Home Server"> > <Component > > Id="HomeServerConsoleTab.MyPanel" > > Guid="xxxxxx-f77a-11dd-87af-0800200c9a66"> > > <File > > Id="HomeServerConsoleTab.MyPanel.dll" > > Name="HomeServerConsoleTab.MyPanel.dll" > > Source="HomeServerConsoleTab.MyPanel.dll" > Vital="yes" > KeyPath="yes" > DiskId="1"/> > </Component> > </Directory> > </Directory> > </Directory> > > <Feature Id="ProductFeature" Title="MyPanel" Level="1" > AllowAdvertise="no"> > <ComponentRef Id="HomeServerConsoleTab.MyPanel" /> > </Feature> > > </Product> > > </Wix> > > Any help is greatly appreciated. Regards, > -- Michael ------------------------------------------------------------------------------ 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
