It really is a good practice to update the version (usually the "build number",
third part of the four part version) every time you build. You can see us
doing that with the WiX toolset here: http://wix.sourceforge.net/releases.
Major upgrades work just fine then.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Colin Bleckner
Sent: Monday, May 05, 2008 11:10
To: Ken MacDonald
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Allow installer to install over itself
Hrm, something like that might worked. Just to make sure I understand what's
going on, it sounds like there isn't a way to do this with out changing the
version number? I'd love to just keep my installer version at 1.0.0 and allow
it to overwrite all other 1.0.0 installations, even though I'm making changes
to the binary it's installing. Yeah, this might lead to a case where an old
binary is installed over a newer one, but that's not really a problem for us.
Also, is the installer's version number supposed to have some connection to the
version of the application that's being installed? Feels a little strange to
keep bumping up the version number if the underlying binary isn't really
changing much.
Colin
Ken MacDonald wrote:
I did something kind of like this for a very lightweight install: I made every
package into a major install, using the ??????? syntax to update the
appropriate UIDs and using a upgradecode, and generated a new version number
each time using the year, month, day, and time of day as the major/minor/rev
number, something like 2008.0502.1645 which is always a newer version than the
one installed - it seems to just install fine over the last one every time.
Details a little hazy as it's been a while, but sounds like it could work for
you.
HTH,
Ken
On Fri, May 2, 2008 at 4:42 PM, Colin Bleckner <[EMAIL PROTECTED]<mailto:[EMAIL
PROTECTED]>> wrote:
Hey guys,
I'm building an application that's going through lots of small revisions
right now. It's annoying to install, though, because we must first
uninstall the previous installation, then install the new one. I'm
trying to figure out how to fix this. The application is internal,
alpha quality stuff, so I don't want to maintain version numbers and
stuff, I think I just want an installer that can install over itself.
Is it possible to do this? I don't want to change GUIDs or version
numbers with every build, I'd just like to have an installer that copies
over the existing files and registry keys. My installation process is
pretty simple (just copying a couple files and setting a few registry
settings). I've been reading through this page, but it seems like more
than what I want or need: http://www.tramontana.co.hu/wix/lesson4.php
I naively tried adding an UpgradeCode to my product then adding an
Upgrade element that references that GUID, but I'm not sure what to do
with it. If I run the exact same installer twice in a row it installs
both times, but if I build a new installer I get the "this product is
already installed" error message. Any suggestions?
Thanks!
Colin
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net<mailto:WiX-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
