Team Foundation Server

warning: Creating default object from empty value in /home/phecht/public_html/ado/modules/taxonomy/ on line 33.

Developer Support Team Foundation Server Blog

Developer Support Team Foundation Server has good inks. For example: Testing Email flow from your Team Foundation Server.

A TF Command file example

Put the following into a script.tfc file called for example.

cd %3
rem Change the current directory from whatever it is to the project folder.
workspace /new /s:TeamServer2 /user:UNO\juan %1BuildWS%2
rem Create a new workspace on the TeamServer2 server as user UNO\juan.
rem Assign a name to the workspace that concatenates the first command line argument (%1) + "BuildWS" + the second command line argument (%2)
get %1 /recursive
rem retrieve the latest version of the first command line argument.
branch %1 %1V%2
checkin /comment:”This is build v%2 of %1”
label %1Build%2 /category:builds /comment:”%1 Build %2” %1V%2
workspace /delete %1BuildWorkspace%2

Keeping labels when the retention policy deletes builds.

If you setup your TFS build server to delete old builds you might not know TFS deletes the label for that build as well. If you one of those old builds you want to have the label you used to build it. Many ways to deal with this issue. Changing the AT web.config is how to change it for all builds. The builds will be deleted, but the labels will remain.


"The build admin can add a flag to the Web.config file on the Application Tier to specify that labels should not be deleted. Here is an example of what that line in the web.config file would look like:

<add key="PreserveLabelsOnBuildDeletion" value="True"/>

Large team considerations for large teams using tfs.

Here is a piece on # of projects and some sql queries.

Building with tfs 2008

Here is an interesting add on: It has many tasks and targets.

I found the "sdctasks" from this site: shows how to build using multiple cores. Also, shows some ability to keep projects from building at the same time.

Finally, seems to offer Wix ability as well.

Development Process tool

Introduction to OpenUP discusses the SDP "Open UP". Yet, it is not just another process doc. It is based on the Eclipse Platform's Eclipse Process Framework (EPF). This allows teams to define work flow using Eclipse.

I need to sharpen up on Team Foundation Server, but if I had the time and choice. I would evaluate EPF.

TFS Other Links came from a presentation I saw here: You can see a java shop convert to TFS.

Also is a good source.

TFS-Cost Benefit Analysis

Discusses the cost not just in dollars but in terms of team pain. Most places do have less than perfect processes for developing and testing code. Does that mean TFS is the only game in town?

Nothing wrong with using Bugzilla or Mantis for Project Management. Even Jira is cheaper.

Also, CVS and Sub version are not perfect but tested in house.

Now I am up at 2 AM looking at posts about TFS costing $1,500 per seat some how.

Syndicate content