That fixed it, I can build 3.8 on my Win7/VS2012 and WinXP/VS2012 environments.
From: Rob Mensching [mailto:[email protected]]
Sent: 21 February 2013 23:50
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] 3.8 build failure
Can you try providing /p:VisualStudioVersion=11.0 on the msbuild command-line
when building?
I expect that is it. If you are building on a machine with both VS2010 and
VS2012 installed then you either have to launch from their cmd prompt (which
sets VisualStudioVersion correctly) or set that variable (environment variable
is fine) yourself. Screwy VS2012 backwards compatible feature.
On Thu, Feb 21, 2013 at 3:31 PM, Rob Mensching
<[email protected]<mailto:[email protected]>> wrote:
Can you provide more of the log file where the error occurs? I'm trying to
figure out which projects are involved in the build that is failing.
wcautil.vcxproj gets built many times.
On Thu, Feb 21, 2013 at 3:02 PM, Neil Sleightholm
<[email protected]<mailto:[email protected]>> wrote:
No VS command prompt (they are too abstract for me <smile>) I just set the
msbuild path to "%SystemRoot%\Microsoft.NET\Framework\v4.0.30319\msbuild.exe"
and build the wix.proj.
This means I get these environment variables:
VS100COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio
10.0\Common7\Tools\
VS110COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio
11.0\Common7\Tools\
VS80COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\Tools\
VS90COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio
9.0\Common7\Tools\
VSEDEFLOGDIR=C:\ProgramData\McAfee\DesktopProtection
VSSDK100Install=C:\Program Files (x86)\Microsoft Visual Studio 2010 SDK\
I have a bunch of SDKs installed so if the build references the registry keys
for these that will probably be set.
Neil
From: Rob Mensching [mailto:[email protected]<mailto:[email protected]>]
Sent: 21 February 2013 22:33
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] 3.8 build failure
Are you launching from a VS command prompt? If so, which one. My builds work
when I don't use VS command prompt for VS2010, VS2012 and VS2010+VS2012.
IIRC, that error happens when the VisualStudio property is not set correctly.
On Thu, Feb 21, 2013 at 2:18 PM, Neil Sleightholm
<[email protected]<mailto:[email protected]>> wrote:
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
