Code Documentation Checkin Policy

  •        0

This tfs checkin policy for Visual Studio 2010 & 2012 checks if c# code is documented the way it's configured in the config of the policy.

http://cdcp.codeplex.com/

Tags
Implementation
License
Platform

   




Related Projects

TfsPolicyPack


This project will provide a few checkin policies for VS 2010.

TFS Code Coverage Checkin Policy


Checkin Policy for TFS 2005/2008 that enforces that the latest test run of the current solution has a total code coverage above a certain, configurable, treshold.

TFS Code Comment Checking Policy (CCCP)


This Team Foundation Server (TFS) checkin policy ensures that the source code contains code comments (/// for C#, ''' for VB.NET) for classes, methods, properties, fields and events before checking it into Team Foundation version control (TFVC).

Check-In Policy Pack for TFS


Check-in policies in Team Foundation Server ensure that code checked into version control meets the defined quality requirements of your team. This policy pack wants to offer the anxious project leader a wide range of different policies to meet their typical needs.

TFS Source Control Client


Team System Version Control Client is used to Create Workspaces, Working Folders, Add files, checkIn and Update Sources of Team System projects in TFS without using Visual Studio 2005.

$log$ / Keyword Substitution / Expansion Check-In Policy (TFS - LogSubstPol)


LogSubstPol is a TFS check-in policy which insertes the check-in comments and other keywords into your source code, so you can keep track of the changes even if you are not connected to TFS. It can be compared with the $log$ (and other) substitition in any other CVS systems.

Visual Studio Extension - Gated CheckIn


Its a visual studio 2010 plugin for Gated Check in. Currently only TFS 2010 is supported as Source Control provider.

Office / SharePoint 2013 Continuous Integration with TFS 2012


Provides a set of PowerShell scripts and a custom TFS Build workflow to build and deploy (for testing purpose) Office / SharePoint 2013 projects using TFS 2012.

MultiTargetSpike - A Visual Studio 2012, TFS Spike for dealing with multi targeting builds


A Visual Studio 2012, TFS Spike for dealing with multi targeting builds

Test Case Import Utilities for Visual Studio 2012 and Visual Studio 2010


Utilities for importing test cases, requirements, bugs from excel and word formats into work items on the Visual Studio Team Foundation Server 2010 or 2012.

TFS Test Steps Editor


Lightweight editing and results publishing for Visual Studio Microsoft Test Manager 2010 test case steps.

Team Build Inspector


An add-in for Visual Studio Team Explorer that monitors the status of build definitions by its latest build, latest good build & underlying source code status.

tfs-strip - Strip TFS Source Control metadata from Visual Studio solutions/projects, within Cygwin


Strip TFS Source Control metadata from Visual Studio solutions/projects, within Cygwin

Search Work Items


This plugin for Team System puts a little search box right into Visual Studio to make it easy to find work items. It is an addin for Team Foundation Client (Team Explorer) and is accessible from the Team menu when you're connected to a Team Foundation Server and is also avail...

jamesmanning-ForbiddenStringCheckTfsCheckinPolicy


TFS checkin policy that allows users to define a particular set of strings that should prevent check (for instance 'DO NOT CHECK THIS IN!')

Team Foundation Server Administration Tool


Member of the Power Toys for Visual Studio Collection - TFS Admin Tool allows a Team Foundation Server administrator to quickly add and modify user permissions to all three platforms utilized by TFS through one common interface.

TFS Event Handler for Visual Studio 2008


The TFS Event Handler makes it easier to notify users of changes to Work Items in Team Foundation Server. You will no longer need to add individual alerts to us

TFS Versioning


TFS 2010 Versioning allows a build master to version assemblies (Assembly Version and Assembly File Version). It does this with version number patterns through the TFS build workflow. You can identify the version patterns in the build definintion or in a version "seed file".