This is an old thread, but I finally got around to figuring out an answer.
There may be a Votive bug, or a VisualStudio bug/feature. Maybe you guys can
tell me.
When you fire up VisualStudio (I'm using 2010) and hit Build/F6 it does not,
per se, build the Default Build Configuration (the one that
Are you not specifying the build configuration you wish to build?
-Original Message-
From: john.burak [mailto:john.bu...@telvent.com]
Sent: Thursday, September 27, 2012 12:08 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] In .wixproj, default Build Configuration ignored
The original issue was that we wanted to specify which configuration builds
by default after launching the IDE with no preexisting .suo file. Turns out
this is dictated by the names of the configurations in the solution.
--
View this message in context:
There is a bug open that the solution builds don't work quite right (
http://sourceforge.net/p/wix/bugs/2993/). My understanding is that this is
an issue with MPF provided by Visual Studio and no one has tracked down how
to fix it in Votive. Your issue sounds like it might be related.
On Thu, Sep
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] In .wixproj, default Build Configuration ignored or
not
settable?
A verbose MSBuild log file should show you how the property values are
changing. If not, I've found sprinkling Message tasks in the MSBuild
A verbose MSBuild log file should show you how the property values are
changing. If not, I've found sprinkling Message tasks in the MSBuild files
is often the fastest way to see why values are not what I want them to be.
Just had to do that today to fix the bundle signing bug. smile/
On Fri, May
It's my understanding that with MSBuild, the configuration and platform used
when none are specified is defined near the top of the project file in the
elements with blank conditions, like this:
?xml version=1.0 encoding=utf-8?
Project ToolsVersion=4.0 DefaultTargets=Build
7 matches
Mail list logo
