On Thu, Feb 14, 2008 at 7:32 PM, Bob Arnson <[EMAIL PROTECTED]> wrote:
> If you're using Votive, why not just build via the .wixproj? That way
> you get the same behavior from developer builds and the official build.
>
> Regardless, WixUI in WiX v3 uses embedded localization sets so you want
> the "cultures" attribute (like it's set in the .wixproj) for the light
> task.
>
Turns out, the build was actually failing after trying to build the wixproj
file. I'm not sure what to make of it though. I turned on verbose output
on my machine where everything works in Visual Studio fine. It's running
light.exe and passing -cultures:en-US into the light program. However on
the other machine, without visual studio installed (but WiX 3.0 installed),
according to the build logs, it's running light, but not passing in the
-cultures argument at all, which explains all the errors.
But now the question is, why is the same WiX install handling the same
wixproj file differently on different machines? Have you encountered this
before? Does it have to do with Visual Studio building it as opposed to
NAnt building it?
-Brendan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
