My product wxs starts as this:
?xml version=1.0 encoding=UTF-8?
?define VERSION=0.3.0?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Product Id=*
Name=!(wix.ProductName) !(wix.TheVersion)
Language=1033
Version=!(wix.TheVersion)
I don't believe that is correct. Visual studio setup projects use 3 digits for
the product version number and my #define only has 3 digits as the version
number but that works.
And regardless of that, I'd tried it with 4 digits and get the same error
message so it doesn't work with 3 or 4.
I'm using Visual Studio integration. Passing a -d to candle is equivalent to
doing a ?define VERSION=0.3.0? isn't it? Using the pre-processor define
works for me.
Using a WixVariable is equivalent to passing -dVersion=0.3.0 to light as
variables are resolved at link time.
Cheers
Russell
This seems to have been reported already (just found the bug database):
http://sourceforge.net/tracker/index.php?func=detailaid=2803055group_id=105970atid=642717
On Thursday, 16 July, 2009, at 08:32AM, rh_maill...@mac.com wrote:
I'm using Visual Studio integration. Passing a -d to candle is
I'm new to wix and have a couple of wix projects in our solution. I'm now
trying to put the UI setup in to a common WixLibrary that our other setup
programs can link to. I'm using Wix 3.0. I've created a library project with
the following code:
?xml version=1.0 encoding=UTF-8?
Wix
I have the following code for the UI in my setup projects:
UIRef Id=WixUI_Minimal/
WixVariable Id=WixUIBannerBmp Value=Banner.jpg/
WixVariable Id=WixUIDialogBmp Value=Dialog.jpg/
This code is actually in an include file that is shared by multiple wix
projects. So Banner.jpg and
Thanks Peter. I am using Wix through its Visual Studio integration. I'd added
the library as a reference to the main setup project. I've now added an
explicit property to the library which can be referenced:
Property Id=WixCommon Value=WixCommon /
Which is referenced from the main
The multiple fragments in a single library does make sense. Thanks for your
help on this.
Cheers
Russell
On Wednesday, 15 July, 2009, at 03:09PM, Peter Shirtcliffe
pshirtcli...@sdl.com wrote:
I see what you mean, especially if youre used to C# references in VS.
The oddness allows you to
I'm trying to put a GUID in to a wix variable but can't seem to make it work.
I've successfully put the same GUID in to a pre-processor define and it works
correctly. Is this a bug in Wix 3 or am I trying to use wix variables
incorrectly.
I've declared the define like this:
?define
OK, I've found the problem. A library is just re-formatted XML just embeds the
WixVariable value as its written in the wxs file. So a solution to this is to
change the WixVariable lines to by:
WixVariable Id=WixUIBannerBmp Value=$(sys.SOURCEFILEDIR)Banner.jpg/
Which then embeds a full
Thanks Brian, this does work (I thought I'd tried this and it didn't before!)
Odd that if I define the GUID as a pre-processor variable it doesn't require
{}'s and if you enter the GUID manually Wix says it doesn't need them.
But it works so great.
Thanks
Russell
On Wednesday, 15 July,
11 matches
Mail list logo
