Sign in
|
Join
|
Help
Baruch Frei
Home
RSS
Atom
Comments RSS
Go
Tags
ALM
Azure
Beta
Blogging
C#
Code Generation
CTP
DEV
DevAcademy3
ITPRO
Linq
MSBuild
MTM
Network
OFFTOPIC
Performance
Reflection
Sela
Team Build
Tech
teched_il
TFS
TFS 2010
TFS API
TFS Power Tools
TFS Web Access
TFS2012
TSWA
Upgrade
User Group
Visual Studio
VS2010
VS2012
Windows 7
WinForms
Workflow
WSS
XML
XPath
Archives
February 2013 (1)
November 2012 (1)
October 2012 (1)
June 2012 (3)
September 2011 (1)
August 2011 (3)
May 2011 (1)
April 2011 (1)
March 2011 (1)
February 2011 (3)
December 2010 (1)
August 2010 (1)
June 2010 (1)
May 2010 (1)
December 2009 (1)
September 2009 (2)
July 2009 (2)
June 2009 (1)
May 2009 (6)
April 2009 (6)
March 2009 (1)
February 2009 (2)
January 2009 (4)
December 2008 (8)
Navigation
Home
All Posts
RSS
Popular Tags
Browse by Tags
All Tags
»
MSBuild
(
RSS
)
Azure
Beta
DEV
ITPRO
OFFTOPIC
Team Build
Tech
TFS
TFS 2010
Visual Studio
VS2010
Windows Azure - Back To The Future
09 September 11 04:22 PM
|
BaruchF
| with
no comments
Last week I was looking for solution how to Build and publish Windows Azure package during Team Build. I found this msdn reference that headline says it was Updated: June 20, 2012 … (While writing this post it still there …) Happy Building .
CustomizableOutDir In Team Build 2010
22 February 11 10:48 AM
|
BaruchF
|
2 comment(s)
The default behavior of Team Build is to override the Output Directory defined in the compiled project and direct all outputs to Binaries Dir. But, sometimes this behavior is not good either because of Solutions dependencies either because we want our outputs in specific structure. In Team Build 2008 there was a predefined property for that reason “CustomizableOutDir” that if it set to true output directories are not overridden. In Team Build 2010 (as part of moving from MSBuild to Workflow...
Msbuild for Website & the slippery “_PublishedWebsites” folder
13 February 11 03:30 PM
|
BaruchF
| with
no comments
I got request from one of our clients about wired behavior of the Team Build. In some of the builds for Web projects the build creates a _PublishedWebsites folder under drop location and arranges all WebSites\WebApplications\WebService under this folder very nice. But in other builds this folder is missing even though all web projects compiled successfully. It just drops all compiled materials under drop location. As I remember it should just work Out Of The Box. For testing I created new solution...
Command Line build – Bug & Workaround
24 August 10 12:04 AM
|
BaruchF
| with
no comments
In the last time I was working on updating one of our clients Build Machines. We got a new muscular (virtual) machine with 2 cores and a lot of memory, but instead of getting faster build they start to fail unexpectedly. It came out that unmanaged (C++) solution that we are building in command line using devenv.com is falling without any meaningful error in the log. I’ve opened Visual Studio in build environment and everything works like a charm, it compiles with no errors. Building in command line...
Debugging Team Build – Now you can !!!
02 July 09 09:13 AM
|
BaruchF
|
12 comment(s)
In the last post I wrote about the new features in the new coming version of the TFS 2010. In the next posts I will try to give a closer look on every feature. TFS 2008 Build script editing In TFS 2008 the build script was written in xml based on Msbuild scripts. Which means that editing the script was pretty ugly and annoying method. This scripts defines the targets and tasks to run in the build but the schema was never updated to recognize all the new targets and tasks so you didn’t really got...
Upgrade your Team Build Tasks from 2005 to 2008
17 February 09 03:17 PM
|
BaruchF
When you upgrade your TFS server from TFS 2005 to TFS 2008 you should take care of upgrading your build scripts. As you know, build configuration has been changed and all build settings like build machine, build directory, drop location, etc’ that used to be stored inside the build script. Now they are stored in a special database (they still exist in tfsbuild.proj but only for backswords compatibility).Here is a basic guide . When you upgrade TFS server the upgrade process takes care of the build...
Create recursive ItemGroup on specific folders-including the folders themselves
25 January 09 04:14 PM
|
BaruchF
| with
no comments
In MSBuild when you want to copy files and save the folder tree you can create a recursive ItemGroup and send it to the copy task . Here is the syntax of declaring recursive ItemGroup : < ItemGroup > < MySourceFiles Include = " c:\MySourceTree\**\*.* " /> </ ItemGroup > but, what if you want to create a recursive item group and include only specific folders and sub folders? For example let’s assume you have this tree: and you want to copy only folders A and C recursively...