[WiX-users] WixLibrary project WixUI declarations

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: http://schemas.microsoft.com/wix/2006/wi";>

[WiX-users] Wix UI images and paths

I have the following code for the UI in my setup projects: This code is actually in an include file that is shared by multiple wix projects. So Banner.jpg and Dialog.jpg don't live in each project folder, they're in a common location. So I've added relative include and reference path

Re: [WiX-users] WixLibrary project WixUI declarations

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: Which is referenced from the main project and this now works. But it seems a b

Re: [WiX-users] WixLibrary project WixUI declarations

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" wrote: >I see what you mean, especially if youre used to C# references in VS. >The oddness allows you to have multiple fragme

[WiX-users] WixVariables and GUIDs

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: And was accessi

Re: [WiX-users] Wix UI images and paths

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: Which then embeds a full path to the file assuming it is in the current folder. This works fi

Re: [WiX-users] WixVariables and GUIDs

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, 2009,

[WiX-users] (no subject)

My product wxs starts as this: http://schemas.microsoft.com/wix/2006/wi";> This fails to compile with the following errors: Error 1 The Product/@Version attribute's value, '!(wix.TheVersion)', is not a valid version. Legal version values should

Re: [WiX-users] (no subject)

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. Ch

Re: [WiX-users] (no subject)

I'm using Visual Studio integration. Passing a -d to candle is equivalent to doing a 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 On Thursday, 16 July, 20

Re: [WiX-users] (no subject)

This seems to have been reported already (just found the bug database): http://sourceforge.net/tracker/index.php?func=detail&aid=2803055&group_id=105970&atid=642717 On Thursday, 16 July, 2009, at 08:32AM, wrote: >I'm using Visual Studio integration. Passing a -d to candle is equivalent to >do