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=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
