Old news...but very cool if you didnt already know....Team Foundation Server Power Tools v1.2 was released.

The Microsoft Visual Studio 2005 Team Foundation Server Power Tool (formerly known as Power Toys) is a set of enhancements, tools and command-line utilities that improve the Team Foundation Server user experience. This release includes two new command-line tools for the developer and three non-command line tools: a process template editor, a set of custom check-in policies, and a test tools build task:

• Team Foundation Server Power Tool Commands (tfpt.exe) - A command-line tool with enhanced functionality for Team Foundation Version Control with graphical user interfaces for some commands.
• Process Template Editor - A tool integrated with Visual Studio for authoring custom work item types and some of the associated process template components.
• Check-In Policy Pack - A set of handy check-in policies to address needs customers have expressed.
• Test Tools Build Task - A tool that allows running unit tests by simply specifying the DLLs, or by specifying a file name pattern in TfsBuild.proj, instead of using .vsmdi files to specify tests to run.

I was a little bummed that the check-in policy pack didn't have any of the policies which I had requested (laughs)(especially since I posted on sending all of your comments). With that aside I couldnt have been happier with this release of the Process Template Editor. The integration with visual studio, the form control, and the validations were a great upgrade in this release. Note: You must first install the Domain-Specific Language Tools for Visual Studio 2005 in order for the Process Template Editor to appear in the Team Menu.

Here are a few screenshots of some of the process template editor features:

Screen - Editing the Process Template

Screen - Editing a work item type

Screen - Previewing the work item control

Screen - Work Item workflow

In the end, I couldn't be happier because this release came at the perfect time for me. I am steadily working on my Master's Project and alot my project will require me to customize the MSF for Agile process template, work items, and reports. Currently, my tentative title is "Customizing Team Foundation Server Process Templates for Software Quality Improvements". I know its quite a mouthfull, but I figured it would be a great way to learn the ins-and-outs of TFS and how to apply some of my MSE Master's knowledge to Microsoft's latest and greatest.

After installing Team Foundation Server and Team Foundation Build, I came across a problem where I would successfully execute a Build on the project, however the build would not appear in the Build Report.

I opened up the Builds database on the TFS Server to see whether not the builds had been recognized. I found that the builds were being stored but that they were not being pulled over into the reports.

This issue is a result of the fact that the reports in TFS are pulled from the data warehouse and the not the Builds Database. In order to decrease the latency between your builds showing up in your Build reports (along with any other TFS changes not showing up in your reports....ex. closing out a bunch of work items and having it reflect on your "Remaining Work" reports) you can change the rate at which the datawarehouse is updated.

The warehouse is updated on a timer so in order to improve the turn around for your reports (or more importantly if you need to pull some reports from some data which has not been updated in the warehouse) then you can modify the update interval by calling this webservice.

Changing the Interval Setting

In Internet Explorer, open the following URL:

http://<tfsserver>:8080/Warehouse/v1.0/warehousecontroller.asmx?op=ChangeSetting

where <tfsserver> represents the name of the Team Foundation Server. A page that contains two boxes labeled settingID and newValue opens.

In the box labeled settingID, type RunIntervalSeconds.

In the box labeled newValue, type the new interval time in seconds.

Click Invoke to change the setting.

Security

To perform this procedure, you must be a member of the Administrators group on the Team Foundation application-tier server. For more information, see Team Foundation Server Permissions.

Manually Kick Off the DataWarehouse Update

1. Go to http://localhost:8080/Warehouse/warehousecontroller.asmx using a browser on the app tier.

2. Click the ‘Run’ link.

3. Press the ‘Invoke’ button.

This will trigger a refresh of the reports.

Brian Keller has provided the opportunity for you to submit any Team Foundation Server questions for his upcoming Visual Studio Team System Channel 9 interview with Brian Harry. If you recall, Brian Harry recently posted about the roadmap for TFS, and in the interview he has agreed to take some questions. I submitted a question regarding TFS's inability to track requirements and if it will be released in subsequent versions...lots of people have been asking this.

Check out already-recorded VSTS Channel 9 videos

One of the common gripes about Team Foundation Server is that fact that it doesn't support out-of-the-box continuous integration. Well Im sure the team had their reasons to exlude this feature in the first release, but hopefully we will get this in a future release. Until, then we will to come up with something on our own. Ben Waldron addresses these concerns in his Agile Development MSDN article on TFS and Continuous Integration.

Brian Harry's latest post lays out the roadmap for Team Foundation Server.

When I think about the TFS roadmap, I think about 3 different categories of things:

Servicing – These are Hot fixes, Service Packs, etc that fix bugs and add new capabilities to versions that have already shipped (today, that means TFS 2005)

Out of Band releases – We call them Power Tools (used to be Power Toys).  These are add-on tools/utilities that enhance the value of already shipped products without actually modifying them directly.

Major releases – These are the big new releases.  The next one is called Visual Studio “Orcas”.  In parallel, we are also actively developing for the release after Orcas, which I’ll describe at a high level.

...........

Please check out his post for a more specifics.

Last month I posted on Mario Rodriguez's blog post in which he was requesting community feedback regarding TFS Version Control Check-In policies. As a result of the feedback which was received, the TFS Version Control team is going to be releasing a Control Check-In Policy Pack.

In his latest post the current goals of the pack of policies are described:

Check-in policy granularity: there is one already in Code Gallery and what we will do is package this, change some of the UI and take out some of the complexity

Work-Item Associations: This is a very cool one that I hope many of you will find useful. You get to specify a query and if the associated work items by the developer are not part of the query results the check-in is blocked. This is very useful when it comes to making sure that check-ins are always associated with approved bugs.

Banned files: this policy allows you to specify a file extension or a regular expression in order to keep files that you don’t want out of version control. This is usually used for dll’s, build artifacts, or some website files that are automatically generated.

Check-in Comments: this policy gets shipped as part of the SDK. It looks at the check-in comments and makes sure it is not blank.

Just a reminder of a few up-and-coming webcasts.

Visual Studio Team Foundation Server HOW TO: Plan for, Install, and Configure

Thursday, November 16, 2006 2:00 PM Central Time (US & Canada)

Visual Studio 2005 and MSDN - a procurement perspective

Thursday, October 26, 2006 2:00 PM Eastern Time (US & Canada)

Momentum Webcast: Best Practices for Source Code Management with Visual Studio 2005 Team Foundation Server (Level 100)

Thursday, November 30, 2006 11:00 AM Pacific Time (US & Canada)

MSDN Webcast: Introduction to Microsoft Visual Studio 2005 Team Edition for Database (Level 200)

Monday, November 20, 2006 10:00 AM Pacific Time (US & Canada)

Visual Studio Team System Demo

Thursday, November 02, 2006 2:00 PM Central Time (US & Canada)

Visual Studio Team System Demo

Thursday, November 30, 2006 2:00 PM Central Time (US & Canada)

Chris Birmele has written a nice paper on Branching and Merging as it relates to Team Foundation Server. Check it out here.

There is an upcoming MSDN chat for Team System. These chats provide a great platform to ask the members of VSTS and TFS all of those insightful questions (or gripes) which you have been saving up. I joined in on the chat last month and found it to be an informative experience. I recommend it to anyone using TFS or VSTS.

The chat will take place Nov 8, 2006 from 10AM - 11AM Pacific Time

MSDN Chats

Mattias Lindberg recently posted on the advantages of VSS over Team Foundation Version Control. The main idea which Mattias was trying to get across was the fact that TFS Version Control is simply not a viable solution for developers who are running a small operation (1 to 2 developers). In order to get TFS up and running, there are several costs and requirements which make VSS a more viable, affordable option (although it may not actually be a better source control system). The hardware, software/OS costs to install TFS can be tremendous so I completely understand where the author is coming from.

Personally, I view TFS as a software process solution which integrates Version Control into the engineering process. Therefore, personal projects which may not require all of the additional TFS features (process guidance, Office Integration, TFS Build, Work Items, etc.) may benefit more from the lightweight VSS alternative. Afterall, there is a large amount of ramp-up time required just to start to get familier with all of the features (and small issues) with TFS.

Eteinne Tremblay has created Team Foundation Server install scripts for both Dual and Single server installations. As everyone who has installed TFS knows, it is not exactly a fun process to manually install all of the prerequisites including IIS, SQL Dev + SP1, Sharpoint Services, additional service packs and then the TFS application itself. Now I wish that at this point I could comment more on how much time that this had saved me, but unfortunately all 3 of the TFS installations which I have undergone at this point have all be done manually. If this really is as easy as it sounds (dropping the installation executables in the folder and letting the scripts do the rest) then I would recommend to anyone.

Read Etienne's blog post on his v2 TFS install scripts.

Click here to read Accient Blog's post which originally had posted the updated scripts. (note: The zip download for the scripts can be found at the bottom of the weblog post)

Download the TFS Install Scripts.

This may appear to be somewhat late news, but it is still worth noting for importance. The Microsoft Solutions Framework Process Guidance which shipped with TFS has been updated. When initially released there were some issues which may have been encountered, but Rob Caron has re-released the zip files to alleviate any of the issues. You can download the process guidance updates for both Agile and CMMI in the links in Rob's Blog post.

Randy Miller has recently published a post discussing the changes which have been made to the newly released guidance files.

The installation guide has been updated for Team Foundation Server. Make sure to download the latest Compiled Help file. Check out Rob Caron's weblog post to see the changes which have been made.

Brian Harry recently posted more information about TFS installation expirations and upgrades. I must admit that this applied to us since we installed the workgroup edition and figured out what had happened while adding our sixth registered user, ugghhh. It was not an exciting time. We are currently in the process of upgrading from TFS workgroup version to the full TFS version, and I'm really hoping that this will work out ok. From the description in Brian's blog post I doubt that we will have any issues (although he was talking about moving from the TFS trial install to the full TFS version).

Also included in the post was an attached application which, when ran on the TFS server, will display that TFS installation Version. Also, you can detect your version without this application by looking opening your Registry Editor. You can find more information on what to look for at Rob Caron's Blog post.

Team Foundation Server Version Detection Screenshot:

Click here to download TFSVersionDetection or you can visit Brian Harry's blog post to download.

There was a recent TFS Version Control Blog post which asked the community for feedback regarding TFS Version Control Check-In policies. The feedback questions were as follows:

1. Would you like us to release a check-in policy pack together with some best practices and ship that out of band?
2. If we do decide to do this then the next question becomes which policies are customers writing themselves that we can standardize and put in the pack?
3. Which policies would customers like to see as examples?

Please visit reply to the post so that we can hopefully convince the TFS Version Control team to release a some standard check-in policies.

The TFS Version Control Blog is ran by Mario Rodriguez who is a program manager on TFS Version Control. Keep that in mind when you post your feedback comments. I know that I would personally love to see a standard check-in policy pack which would handle the most common policies. Due to the fact that these policies are assigned on the server, but need to be enforced on the client, has been somewhat of an issue for myself. Out of curiosity...Is there any standard approach to making these policies. I do understand that we need to override the methods from the PolicyBase class, but is there a recommended way to deploy these policies to all of the clients?

It appears the channel9 will be adding an additional VSTS tag for all Visual Studio Team System releated content.

We recently started tagging new Visual Studio Team System-related content on Channel 9 with a VSTS tag to make them easier to discover. I also just finished tagging all of the older Team System-related content as well. There were several great videos out there, including some that I had never even seen before!

Brian Keller's blog post provides some examples of some videos which can already be found on Channel9. Samples included Application Designer Videos, Code Profiler and Source Control Management. Also there are a few videos which are related to TFS third parties and Microsoft Research Project tools.

View all VSTS tagged content @ channel9.msdn.com

One of my most favorite features with TFS Version Control and Team Foundation Power Toys has to offer is Annotate. With annotate every single line of source code labeled with:

1. The user who made the last changes on each individual line of code
2. The changeset associated with the annotated section
3. The date of the changeset
4. A right click menu which gives you acces to - the changeset details, the history of the file, and the ability to annotate an the previous changeset version.

TFS Annotate Screenshot

Click here to download the latest version of TFS Power Toys

Brain Harry gives us an insight into a few of the changes that we should expect in the next refinement of Annotate.

Brian Harry has provided a list of the Bug fixes we should expect for the Team Foundation Server Service Pack 1. The fix I was most excited about was the common MS Project issue where resources could not be mapped to TFS because a comma was being used the separator in our domain accounts.

Yeah now I can change back my List separator from the ";" to the ",". (Not that I ever noticed any issues from having this setting).

For some reason we started getting the error TF42026 when we attempted to execute our builds. I found this great blog post from Tom Wisnowski which gave a step by step checklist of things to check in order to resolve the issue.

Turns out our this error was being caused from the fact that our Team Build Service was not running.

2. Make sure the Team Build Service is running. Open the services MMC snapin and look for Team Build Service. Make sure the service is running. Also note the account that the service runs as; you will need it for the next step

It turns out that we have installed the TFS Workgroup edition which translates to the fact that we can have a maximum of 5 registered users on our TFS environment. I guess I should have done a little more research into the licensing issues involved with our MSDN subscriptions but it was such an interesting opportunity to:
1. Install TFS and get it up and running with all of its individual components.
2. Convince our department that a move toward this technology would be a step in the right direction.
3. Gain access to a pilot project which would be used as both a model for future projects and a platform for learning all of the ins-and-outs of using TFS throughout the entire lifecycle of a so