Check for Warnings/Errors Check-in Policy (2008)

A couple of weeks ago, I posted on an update for the Check for Warnings/Errors Check-in Policy for Visual Studio 2010 / TFS 2010.  This version was posted here on the Visual Studio Gallery.  Since then, I’ve received some questions about an update for the Visual Studio 2008 / TFS 2008 version of this check-in policy as the one I posted last September had an issue when checking in source code from the command line.

I have now also posted an updated version of the Check for Warnings/Errors Check-in Policy for Visual Studio 2008 / TFS 2008.  If you’re still using TFS 2008 (and I’m sure a lot of you are) then you can download the updated check-in policy here.

Usage:

To add this check-in policy to your Team Project:

1. Download and install the Check for Compilation Warnings and Errors Check-in Policy.  NOTE: Anyone checking in code will need to install the check-in policy on their local development workstations.
   
2. Within the Team Explorer in Visual Studio 2008, right-click on the desired Team Project and select Team Project Settings->Source Control.
   
   
   
3. Click on the Check-in Policy tab, select Check for Compilation Warnings and Error Policy and click OK.
   
   
   
4. Click on the Edit button and select the level of Warnings and/or Errors to check for.
   
   
   
5. Click OK and OK to close the dialog windows.

Once installed and configured, the check-in policy works like any other.  You can check the Pending Changes window for violations as seen in this screen shot:

Compatibility:

This version of the Check for Compilation Warnings and Errors Check-in Policy supports Visual Studio 2008 and Team Foundation Server 2008.  The Visual Studio 2010 version is available here.

OTSUG – Migrating to TFS 2010

Last night, Russ Wagner and I met with the Omaha Team System User Group to present on “Migrating to TFS 2010: Lessons Learned”.  Once again, Farm Credit Services of America hosted the event and provided pizza for the attendees.

Here’s the description of the talk we gave:

In this presentation, Jeff Bramwell and Russ Wagner will discuss the steps taken to upgrade to Team Foundation Server 2010.  The talk will cover up-front planning, tasks that need to be completed in the process, and how to plan for contingencies.  They will also cover various lessons learned along the way.  After the session, they will open it up for questions and answers to give attendees a chance to ask questions as well as share experiences with each other.

It was a small group but everyone came prepared with questions which made for a great and interactive discussion.  We enjoyed the opportunity to share some of the lessons we learned from our experiences while migrating from TFS 2008 to TFS 2010.  All in all, it was another great user group meeting!

If you’re interested in the PowerPoint slides, they’re available here.  For more information about the Omaha Team System User Group:

• Visit us at www.OTSUG.org
• Follow us on Twitter at twitter.com/OmahaTSUG
• Subscribe to the OTSUG Announcements RSS feed
• Subscribe to the OTSUG and Other Events RSS feed

TFS Administration Tool v2.0 Released

With each release of Team Foundation Server, administration gets a little easier.  The release of TFS 2010 introduces the Team Foundation Administration Console (TFS Admin Console) providing a much simpler approach to administering Team Foundation Server.  However, even the TFS Admin Console does not provide any support for managing permissions between Team Projects, SharePoint, and SQL Server Reporting Services (SSRS).

That’s where the Team Foundation Server Administration Tool comes in…

Here’s the official description from the TFS Admin Tool site:

The TFS Administration Tool allows Team Foundation Server administrators to manage user permissions on all three platforms utilized by Team Foundation Server: Team Foundation Server, SharePoint, and SQL Server Reporting Services. The tool also allows administrators to easily copy user permissions among team projects and to easily identify any missing permissions on any of the three platforms.

If you manage user permissions for any number of Team Projects, this utility is a must have!

As of a few days ago, Version 2.0 of the TFS Admin Tool was released.  This release focuses on resolving several bug fixes and introduces a new feature – User Import.  The new User Import feature allows you to easily copy user permissions from one Team Project to another – very handy!

Version 2.0 supports TFS 2005, 2008, and 2010 – with some caveats.  Before installing the Team Foundation Server Administration Tool v2.0, you must have the following installed:

• Visual Studio Team System 2008 Team Explorer
• Microsoft Visual Studio 2008 Service Pack 1 (to update the above Team Explorer to SP1)
• Visual Studio Team System 2008 Service Pack 1 Forward Compatibility Update for Team Foundation Server 2010

NOTE: Even if you have Visual Studio 2010 installed, along with the Visual Studio Team Explorer 2010 client, you will still need to have the Team System 2008 Team Explorer client (with SP1) installed.  The TFS Admin Tool is currently compiled against the TFS 2008 Object Model and therefore must have the referenced assemblies installed on the client machine.  At some point in the future, once some internal code refactoring has taken place, there will most likely be a version compiled directly against the TFS 2010 Object Model that does not require any of the TFS 2008 assemblies to be installed.

So, download the tool and try it out.  Please provide feedback on the project site in the Discussions or Issue Tracker tabs.

Check for Warnings/Errors Check-in Policy

A while back, I wrote about the Check for Warnings/Errors Check-in Policy – a custom check-in policy that I had developed for Team Foundation Server 2008.  Yesterday, I published version 2.1, updated for Team Foundation Server 2010, to the Visual Studio Gallery.  The features are the same as the TFS 2008 version with a couple of exceptions:

1. You now have the ability to restrict the set of warnings to Code Contract warnings only.
2. The settings for the check-in policy are now stored as TFS properties (more on this in an upcoming post).

Here are the details…

Usage:

To add this check-in policy to your Team Project:

1. Download and install the Check for Compilation Warnings and Errors Check-in Policy (see Where to Download below).  NOTE: Anyone checking in code will need to install the check-in policy on their local development workstations.
2. Within the Team Explorer in Visual Studio 2010, right-click on the desired Team Project and select Team Project Settings->Source Control.
   
   
3. Click on the Check-in Policy tab, select Check for Compilation Warnings and Error Policy and click OK.
   
   
   
   
4. Click on the Edit button and select the level of Warnings and/or Errors to check for.  If you select Warnings, you can optionally restrict the set of warnings to Code Contract warnings only by checking the Code Contract Warnings Only checkbox.
   
   
   
   
5. Click OK and OK to close the dialog windows.

Once installed and configured, the check-in policy works like any other.  You can check the Pending Changes window for violations as seen in this screen shot:

Compatibility:

This version of the Check for Compilation Warnings and Errors Check-in Policy supports Visual Studio 2010 and Team Foundation Server 2010 only - it is not compatible with Team Foundation Server 2008.

Where to Download:

There are two options for downloading:

1. You can download this check-in policy directly from the Visual Studio Gallery – here.
2. From within Visual Studio 2010, you can use the Extension Manager to locate and download the check-in.  To do this:
   1. Click on Tools—>Extension Manager.
   2. Click on the Online Gallery “tab” on the left side of the Extension Manager dialog.
   3. In the Search Online Gallery field, enter “check for warnings” and press Enter.
   4. Locate the “Check for Compilation Warnings and Errors Policy” (at the time of this writing, it is the only item in the search results) and click Download.

If you have any feedback, please utilize the “Reviews” and/or “Discussions” tab on the gallery link above.