Browse by Tags
All Tags »
Team Build (
RSS)
So, you want to install team foundation server...It is about time :) This post is referring to those of you who already decided on Team Foundation Server and tools as an ALM supporting platform and want to set up the machines that will host the Team Foundation Server. For those of you who just want to play with it for either evaluation or for learning, I suggest you use a Virtual PC (an image) or a trail version. The Basics Prepare one machine and virtual machine. The first machine will hold the...
In Team System 2005 there is a limit for the location of the TeamBuildTypes folder. The TeamBuildTypes contains all the build type definitions and once you create your first build, the folder is created and added to the source control under the team project route. You cannot change the location by moving it to a child folder because the build requires that the TeamBuildTypes directory to be a folder of the team project for it to show up in the build type tree view. For me this is a problematic solution...
My motivation to initiate the team build from the command line was the need to perform nightly build. To do so I needed to create an executable or a batch file that I can schedule using Windows scheduler. So the first step for me was to create a batch file: SET TFSDIR="D:\Program Files\Microsoft Visual Studio 8\Common7\IDE\" SET TFSSVR="TFS Server" SET TEAMPROJECT="TFS Project" SET BUILDTYPE="TFS Team Build Type" %TFSDIR%TFSBuild.exe start %TFSSVR% %TEAMPROJECT...
In order to compile .NET solutions all we need to do is indicate the path to the solution. It should look something like this: < SolutionToBuild Include = " $(SolutionRoot)\Application Services\Controls\Controls.sln " /> However, when it comes to native C++ solutions, the above line will not work. What should we do? We need to compile the solution from the command line. There are three tools that can help us compile the solution: devenv.exe cl.exe vcbuild.exe The devenv.exe is a process...
This is something I did not expected. Apparently, in order to run unit tests written in Visual Studio Team For Developers during build it is required to install the Tester edition. The Tester Edition comes with a Test Manager window that allows you to create test lists. Team Build will use those test lists during the build process. I think that Microsoft got it wrong here and they should allow the Developer Edition to create a test list using the Test Manager window.
I am working on an automatic build for one of my customers. When I initiate the Get task that gets all the sources from the Team System Version Control, the operation failed with an error that the path exceeds 260 characters. This is apparently a common issue in Team Build. The limit for the 260 characters comes from windows. That means that this is not a Team build limit, rather a windows limit. Aaron Hallberg wrote a good post about it.
Today I got an email from a college blogger Adlai Maschiach . He asked me to write a post about the VSTS Guidance on CodePlex. SRLTeam has published couple of months ago a post about it, however it was recently updated. Here is a list of all the new entries that have been added to the guidance. The guidance contains useful information about team system related issues. You can find white papers, videos, links and much more. I encourage you all to check it and contribute as possible ;)
In one of my projects I had to initiate the deploy operation on my database project during the team build. Here is an article that describes how to just that. An important comment I would like to add is the fact that we need to manually change the .proj file. The link contains information about it, however to further emphasize it, here is the explanation: "The target connection and database are stored in the ProjectName.dbproj.user file, which is user specific and not typically checked in to version...
