Thanks. I figured those approaches out last March. I am trying to keep it
simple though. Ideally a customer would be able to just create a project,
check in their code, create a stock build definition and have it build first
try. I'm guessing that in a month or two the stars will align and this will
be possible. It's possible today if I exclude C++ CA's from the scope.
----------------------------------------
From: "Markus Wehrle" <mar...@laika42.com>
Sent: Saturday, October 26, 2013 12:16 PM
To: "WiX toolset developer mailing list" <wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] Build C++ Custom Actions on Hosted TFS Build
Controller Fails
There is no need to install WiX on the build machine. You have several
possibilities to come around this and it is also possible to use different
versions of WiX and select a WiX version in your build definition. Have a look
in my blog:
http://www.laika42.com/Blog/tabid/92/ArticleID/5/language/en-US/Default.aspx
Using one of the described options it is possible to build with WiX 3.8 or even
with WiX 4 on a hosted controller. If you want to use possibility 4 and use it
with VS 2013 you have to modify the XAML and point it to MSBUILD 12, because I
didn't update the XAML yet. From: Christopher Painter
[mailto:chr...@iswix.com]
Sent: Samstag, 26. Oktober 2013 17:46
To: WiX toolset developer mailing list; WiX toolset developer mailing list
Subject: Re: [WiX-devs] Build C++ Custom Actions on Hosted TFS Build Controller
Fails I've figured out part of it.
On my dev box I have VS2013 RTM. On my on-prem build server I have VS2013 RTM
and TFS 2013 RTM. On my TFS Cloud instance a new project creates a
DefaultTemplate.11.1.xaml build process that when runs picks MSBuild 4.0.
Passing /tv:12.0 doesn't help. I am unable to build. The build process does
not expose a parameter for overriding the MSBuild ToolsVersion. If I modify
the XAML and point it to MSBuild 12.0 then everything builds correctly.
However when I try to build on the cloud hosted build controller I get a new
error (it gets farther at least):
c:\a\src\nxlog-ce-customactions\stdafx.h(17): fatal error C1083: Cannot open
include file: 'wcautil.h': No such file or directory
[C:\a\src\nxlog-ce-customactions\nxlog-ce-customactions.vcxproj]
If I go back to my onprem server and uninstall 3.8 and reinstall 3.7 I get the
same error. So obviously this will all eventually work once WiX 3.8 gets
released and the TFS Service team(s) get the default templates updated and WiX
3.8 on the build image.
So, all in all, WiX 3.8 is looking very good in my extensive and odd ball
testing scenarios. ( For those who want t know, my goal is to be able to
create WiX C++/C# custom actions, installers and bootstrappers using nothing
but free tools. VS Integrated Shell, VS Express Edition, WiX and IsWiX and
TFS Hosted Build Controllers. This helps my customer value proposition for
small businesses that are not visual studio shops and don't have MSDN or
InstallShield subscriptions. )
----------------------------------------
From: "Neil Sleightholm" <n...@x2systems.com>
Sent: Saturday, October 26, 2013 9:44 AM
To: "WiX toolset developer mailing list" <wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] Build C++ Custom Actions on Hosted TFS Build Controller
Fails I found some notes I made for a VS2012 C++ project, not sure if I had
to do this and install VS but it might help: Edit
Microsoft.Cpp.x64.targets: In LinkEmbedManifest target, change Link
attributes: DelaySign ="%(Link.DelaySign)"
KeyFile ="%(Link.KeyFile)"
http://blogs.msdn.com/b/vcblog/archive/2011/03/11/10140139.aspx Add
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE" to path
Install "Windows SDK for Windows 7 and .NET Framework 4" Build with
PlatformToolset=Windows7.1SDK Is VS installed on your
build server? I have found that this is required for C++ projects, at one point
MS did include the C++ tools and libs in the SDK but then removed them in the
Windows 8 version. This is a bit of pain as I don't like the idea of polluting
my build server with VS. Neil Oh great. It seems I did
have RTM on my dev laptop and RC on my build server. Now that I upgrade my
build server to RTM I can't build my C++ project on my build server or the
cloud hosted build server.
Something seems really wrong if I can't just create a C++ project, check it in
and tell it to build. Builds on my machine....
Any thoughts? Off to research.
----------------------------------------
From: "Christopher Painter" <chr...@iswix.com>
Sent: Saturday, October 26, 2013 8:14 AM
To: wix-devs@lists.sourceforge.net
Subject: Re: [WiX-devs] Build C++ Custom Actions on Hosted TFS Build Controller
Fails
Oh wait, nevermind. I'm all wrong. I have RC installed on my dev machine and
build server. I forgot to upgrade them. Let me do that and retest.
----------------------------------------
From: "Christopher Painter" <chr...@iswix.com>
Sent: Saturday, October 26, 2013 8:07 AM
To: wix-devs@lists.sourceforge.net
Subject: Build C++ Custom Actions on Hosted TFS Build Controller Fails
I created a C++ custom action project using WiX 3.8 and VS2013. It builds on
my on-prem build server with VS2013 installed but fails to build on the Hosted
TFS Build Controller.
FWIW, I also created a stock C++ project and it has the same behavior so it
doesn't seem to be a WiX problem per say.
Now according to this page:
http://tfs.visualstudio.com/en-us/learn/hosted-build-controller-in-vs#software
VS 2013 RTM is supposed to be installed on the build server. I'm not the best
C++ developer in the world so I'm wondering if anyone can shed any light on the
following build error. It might be possible that WiX modeled it's project type
after something that was broken and could be made better as a result of this.
Build started 10/26/2013 12:50:11 PM.
Project "C:\a\src\nxlog-ce-customactions.sln" on node 1 (default targets).
ValidateSolutionConfiguration:
Building solution configuration "Debug|Win32".
Project "C:\a\src\nxlog-ce-customactions.sln" (1) is building
"C:\a\src\nxlog-ce-customactions\nxlog-ce-customactions.vcxproj" (2) on node 1
(default targets).
C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.Cpp.Platform.targets(44,5):
error MSB8020: The builds tools for v120 (Platform Toolset = 'v120') cannot be
found. To build using the v120 build tools, either click the Project menu or
right-click the solution, and then select "Update VC++ Projects...". Install
v120 to build using the v120 build tools.
[C:\a\src\nxlog-ce-customactions\nxlog-ce-customactions.vcxproj]
Done Building Project
"C:\a\src\nxlog-ce-customactions\nxlog-ce-customactions.vcxproj" (default
targets) -- FAILED.
Done Building Project "C:\a\src\nxlog-ce-customactions.sln" (default targets)
-- FAILED.
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
