Yes,
Add in a in your wix project file and and
SourceDir will look there!
>From my project file:
..\BuildTools\WiX\3.0.5419.0\
$(WixToolPath)Wix.targets
wixtasks.dll
False
..\Build\Release
$(DefineConstants);BuildVersion=$(Version);ProductDescription=$(Description)
Regards,
Aske
Giora, do your versions differ by more than the fourth digit?
I have found that if you install 1.0.0.0 and then 1.0.0.1 they will both be
listed as installed.
Incrementing the third digit (ie 1.0.0.0 to 1.0.1.0) the older version will be
replaced.
To enable replacement also by fourth digit versi
Is there any way to accomplish this via a Visual Studio build?
-Original Message-
From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com]
Sent: Sunday, December 06, 2009 7:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cabinet does not contain an
Unfortunately the documentation is a bit vague on this particular
subject. Basically you can use one or more "-b" parameter's with Light
(http://wix.sourceforge.net/manual-wix3/light.htm) to indicate what
directories should be searched when looking for files in 'SourceDir'
Sascha
On Mon, Dec 7,
I'm using a fragment outputted from heat as my project includes a few
thousand files, so in VS I have a sourcefile.wxs:
http://schemas.microsoft.com/wix/2006/wi";>
What determines what the folder "SourceDir" is? Since this is
1. Package/@Id is optional but "*" is ok.
2. Order doesn't matter
3. Not sure I understand
Is your UpgradeCode/@Id fixed for both installations? Do you have
RemoveExistingProducts scheduled somewhere? Do you have an
section?
You shouldn't need to update using that command line, it should just
wo
Neil Hello
Thanks for the fast answer.
I looked at code in the URL you sent me. It looks for me that my code
is similar.
The differences I found where:
1. My code has It sounds like you haven't got the upgrade code correct, there is a
> sample here
> http://neilsleightholm.blogspot.com/2009/01/
Ondrej Zarevucky wrote:
> But we would like to somehow be able to select which programs/features
> not to remove and reinstall during the update. The ideal solution would be:
> "ADDLOCAL=MainFeature,ProgramOne KEEPOLD=ProgramTwo"
>
MSI doesn't have anything like that; major upgrades work by re
Henry Sheldon wrote:
> How would I either force the button
> to be pushed when entering the dialog or break up these commands into a
> custom action and get it to run when entering the dialog. I don't mind if
> it runs before entering just as long as the properties are loaded once the
> dialog is
It sounds like you haven't got the upgrade code correct, there is a
sample here
http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrade
s.html that might help.
Neil
-Original Message-
From: Giora Keinan [mailto:grkei...@gmail.com]
Sent: 06 December 2009 12:54
To: wix-use
hello
Each time I am running a new upgrade, the installer add one more entry
in the add remove program.
How can I made an upgrade without adding it to the add remove program
(leaving only one add remove in place).
Thanks
Giora
--
-
Giora Keinan
C
11 matches
Mail list logo