Don't know the answer, but surely interested when you find out how. I
understand you update by a complete uninstall followed by a new
install. How about the other way around: first install the new
version and then uninstall the old one? My experience is that in that
case a registry key
You probably know this stuff but Bob posted some interest information
here: http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/
Neil
-Original Message-
From: vexilar [mailto:s...@sorna.com]
Sent: 16 January 2009 23:56
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
Vidya Kukke wrote:
One last thing, I was wondering how come if it has not been localized in
japanese I get warnings only for a few strings? Is it that these are new and
have been introduced only in 3.0 but the rest of the strings were in 2.0 and
are available for use as-is in 3.0?
The
Colin Fox wrote:
my_cool_software%24%28filever%29
So is variable substitution not allowed in output names? Or is this a bug?
It would require explicit support, at least in Votive. As it's
rare/dangerous, I doubt Votive supports it. You can always do it with a
post-build target.
--
Thanks a lot. I'm converting from using Visual Studio Setup Projects, so I
think the easiest thing to do will be to schedule REP Before/After
InstallInitialize.
Neil Sleightholm wrote:
You probably know this stuff but Bob posted some interest information
here:
5 matches
Mail list logo
