Thanks Justin-something else that I just noticed was that if you're
working with a library project, you can't add a reference to it in an
installer: you need to reference the compiled wixlib directly. This
works, but if it's possible to reference the project directly (so the
linker will use the current IDE configuration's version) it might make
more sense.
Actually, another thing that came up when working with libraries was
binary files for a GUI (bitmaps etc). Is there not a way to embed
bitmaps in the wxl library? I've added a bitmap with the <Binary> tag
and built the library, but then the Wix project that links against this
library needs to contain the bitmap. I'd like to have the graphics
carried with the library (ideally overrideable), the same way that
strings are. Is there documentation somewhere that explains how to do
this?
Thanks again for the help.
Chris
From: Justin Rockwood [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 4:04 PM
To: Chris Bardon; Ashman, Jared; Levi Wilson; Simon Dahlbacka
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Votive v3 and UI
Good points. I don't necessarily like defaulting to en-US, just because
WiX is being used quite heavily in other locales (German, Russian, and
Dutch are ones that come to mind). However, defaulting to the OS culture
makes a lot of sense. Let me know if you have any other suggestions as
you dig more into your project.
Thanks,
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
Bardon
Sent: Tuesday, March 13, 2007 10:41 AM
To: Ashman, Jared; Levi Wilson; Simon Dahlbacka
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Votive v3 and UI
Ah, that did it, thanks. Probably just a bug with the settings not
being saved in both cases. I know I've done the same thing more than
once.
As for Justin's question, the only thing I can think of off the top of
my head is to at least automatically define the en-US culture when
adding the reference to the UI DLL. If nothing else, this will mean
that anyone who wants to compile to en-US will be able to do so without
digging through properties, and others will be able to find the culture
settings if they need to. Picking up the automatically included culture
from the OS could also be an option, as would automatically including at
least one culture in the properties, and then ignoring it if it's not
needed (i.e. not compiling with the DLL). I'll see what else I come up
with as I start venturing into more custom UI along the way (which I
suspect will introduce a bunch of new questions).
Chris
From: Ashman, Jared [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 1:28 PM
To: Chris Bardon; Levi Wilson; Simon Dahlbacka
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Votive v3 and UI
Chris,
If you add the en-US to the field, then open the advanced properties
below that, then save, it does save the culture.
The important step is the advanced properties for some reason.
Jared M. Ashman
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
Bardon
Sent: Tuesday, March 13, 2007 11:39 AM
To: Levi Wilson; Simon Dahlbacka
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Votive v3 and UI
I noticed that field, but adding a culture value to it doesn't appear to
do anything. I tried en-US, en-US;, and even the example en-US;ja-JP
listed below the textbox, and I still got the same errors. Adding the
wxs file directly seems to be the only thing that works.
From: Levi Wilson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 12:35 PM
To: Simon Dahlbacka
Cc: Chris Bardon; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Votive v3 and UI
Maybe that's what it was...that it was TOO easy :-) I usually miss
those.
On 3/13/07, Simon Dahlbacka < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > wrote:
Yes, (at least "semi obvious")
Using votive you select project properties (right-click project ->
properties, select linker tab) specify e.g. "en-US" in the Cultures
textbox, and add a reference to WixUIExtension
On 3/13/07, Chris Bardon < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > wrote:
Thanks for the reply-I managed to get it to work by adding a copy of the
.wxl to the project, but I can't find anywhere to modify the light
command line in the project. Am I just missing something obvious?
On a semi-related note, is there something special you have to do with
Votive to customize bitmaps from one of the UI libs? I tried creating a
bitmaps directory, below the wxs file, but it seems to be ignored
(regardless of whether the new bitmaps are added to the project or not).
Is it not possible to customize the dialogs when using the
WixUIExtension DLL? I'm planning on creating my own UI lib based off of
Mondo, but I'd like to be able to customize it with different graphics
when referenced in different setups.
From: Levi Wilson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2007 11:50 AM
To: Chris Bardon
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Votive v3 and UI
When using WiX UI stuff from the WixUIExtension DLL in version 3, you
need to add:
"-ext WixUIExtension -cultures:en-us"
To the light command-line. This should take care of a lot of those
warnings.
On 3/13/07, Chris Bardon <[EMAIL PROTECTED]> wrote:
I've been going through the tuorial at http://www.tramontana.co.hu/wix/
and adapting to some of the v3 changes as I go, and I've run across a
problem with adding UI elements. If I put in the UIRef elements <UIRef
Id ="WixUI_Mondo" /> and <UIRef Id=" WixUI_ErrorProgressText " /> I get
an unresolved symbol reference. Makes sense, since there's no reference
to the UI lib. I checked in the target directory for the Votive/WiX MSI
from the website though, and there's no wixlib files in the install
directory. There's a WixUIExtension.dll that I can reference, but this
doesn't seem to have any of the strings defined (LGHT0102 gets raised
552 times). It looks like I have to link using the WXL file for the
language, but none of the WXL files are installed with the package. Is
there no way to build an installer without downloading the source?
Since I'm trying to set up a build process for Wix editing/installer
creation where any developer on the team can edit/publish installers,
I'd rather have everything they need to be encapsulated in a
redstributable (i.e. not a separate source download). Is there just
something that I'm missing with getting Votive to build using a UI?
Thanks for the help
Chris
------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
