Feature Builder Power Tool + Check-In Policy Builder = You focusing on features and not adminis-trivia/packaging

Visual Studio Gallery - Check-In Policy Builder

“This feature extension for Visual Studio 2010 was created using the (great) Feature Builder Power Tool and provides an easy way to create your own custom check-in policy for Team Foundation Server.
All you have to do is implement the logic. Don't care about packaging etc, because it's all done by automation.

When you install the extension you will find a new project template in VS called Check-In Policy Builder. Open it to trigger a wizard and then simply follow the guidance in your guidance explorer.

…”

While TFS Check-in policies should be used with care, I really dig the idea of this approach in creating them. Kind of seems that this will make it almost too easy to create check-in policies!? lol

Here’s some snaps of it in action:

 

Related Past Post XRef:
Feature Builder power with drag and drop simplicity - Instant Feature Builder v1 (Think “Drag and Drop Map/Code files/Docs/Guidance in and vsix out”)
Feature Builder v1.0 Released (Remember, this is the tool that helps build tools… The Power Tool for Visual Studio Power Tools)
Feature Builder Power Tool Preview updated for VS2010 RTM – Think “Extension to help build Extensions,” or “Power Tool for Power Tools…”
“Feature Builder Power Tool” Preview Released – A power tool to help you build tools/extensions/etc for Visual Studio 2010, a tool to help build tools…

Wish you could sync your TFS Check-in Policies across your team? Have the TFS Power Tools? Then you already can…
Copy Checkin Policies - Free Command Line Tool to Copy TFS Checkin Policies from one Project to Another.
Team Foundation Server Check-In Policies
"Visual Studio Custom Checkin Policy Template"
Another TFS Checkin Policy - Code Comment Checking Policy
TFS Check In Policies, Code to Police Code