Using Team Foundation Server to Develop Custom SharePoint Products and Technologies Applications

Thinks

There is a great resource on MSDN that dives into using Team Foundation Server as part of your development toolset and practices for development of SharePoint applications.

What are some things you could use this for? Glad you asked as it is in the article.

The following is a list of common SharePoint customizations that can be included in a Visual Studio solution:

• Feature

• Feature Event Receiver

• Site Definition

• List Definition

• Field Type Definitions

• Timer Job Definitions

• Event Handler

• Coded Workflow

• Custom Web Part

• Custom Layout Page

• Feature Stapling

• Site Template

• List Template

• Content Types

• Column Template

• Delegate Control

• Custom Form Template

• Custom Action

• Workflow Activity

• Document Converter

• IM Policy

• Security Policy

• BDC Definition

• Pluggable Authentication Provider

• Pluggable Single Sign-On Provider

• STSADM Command Extensions

Wouldn’t it be nice if there were templates for some of the common items? The authors thought about and wrote that as well.

Visual Studio 2008 Project Templates

• Web Part

• Team Site Definition

• Blank Site Definition

• List Definition

• Empty SharePoint Project

Visual Studio 2008 Item Templates (items that can be added into an existing team project)

• Web Part

• Custom Field

• List Definition (with optional Event Receiver)

• Content Type (with optional Event Receiver)

• Module

• List Instance

• List Event Handler

• Template

Links

• Using Team Foundation Server to Develop Custom SharePoint Products and Technologies Applications
• Eric Charran has a great article at https://msdn.microsoft.com/en-us/library/bb428899.aspx entitled “Team-Based Development in Microsoft Office SharePoint Server 2007” that helps build understanding of SharePoint development.
• Don’t forget the Microsoft Office SharePoint Server 2007 Developer Portal 

Clinks

• GREAT
  • Some definitive guidance on Application Lifecycle Management and SharePoint Development
• SOMEWHAT GREAT
  • The development story for SharePoint is maturing. Still a pain point for some developers, but it is improving.
• NOT SO GREAT
  • Still have to read it
  • Definitely have to practice it
  • I wish it was easier for the complete SharePoint Stack (e.g. SharePoint Designer)