Allen Clark

Update: we’ve published the install guide here: https://msdn.microsoft.com/en-us/Library/vs/alm/TFS/setup/overview. Feel free to post comments or questions on that here as well as leaving feedback directly on the MSDN page.
We’re wrapping up work on a new install guide for TFS 2015. Here’s what we have for a dual server configuration.

The guys behind the All-In-One Code Framework published a sample on using TFS events earlier this month. I’m not sure, but it may have been thier first sample covering TFS. They have more on their backlog. You can suggest sample ideas, and vote on other suggestions,

We’ve just updated to the Team Foundation SDK content ( Extending Team Foundation ) to include VB samples alongside the C# samples that we had previously published.
We’ve also added some new sample code for working with the version control APIs:
…(read more)

Once we identified most of the items (stories) in our backlog, we started to prioritize them. In our first pass, we adapted a technique that Mike Cohn teaches called Theme Scoring . I say adapted because we didn’t identify a small number of themes and rank them using this technique.

In the past, we managed our work by defining the topics that we need to write, and then estimating and prioritizing the work to write those topics. Before VS2010, that worked really well. We documented the features that the product team created.

I have posted a couple of series on how we plan content work for Team Foundation, one in 2007
Planning the Sprint
Tracking Work Items
Reporting Status
and the other in 2009.
How we Track Content Work
Managing Technical Reviews in TFS and SharePoint
Reporting Progress
Well,

I’ve just posted the Team Foundation schema files for process templates and work item types on Code Gallery: http://code.msdn.microsoft.com/TFSchemas/Wiki/View.aspx?id=25933 .
You can drop the schema files in Program FilesMicrosoft Visual Studio 10.0XmlSchemas and Visual Studio will validate your work item types or process template files using the appropriate schema.

First, a caveat: VS 2010 SP1 Beta recently shipped with a go-live license. This post is not about that. If you have VS 2010, and you install VS 2010 SP1 Beta, you’ll get all the new bells and whistles in SP1.

Back in January, I wrote this post that showed that we really needed to change directions on the SDK content. The major elements of the new approach are
Throw out what was there because it wasn’t working
Deliver a new set of SDK content that covers at least the core elements of the client object model.

We just published updates to the Team Foundation SDK , which now covers the server object model . We’re making some other changes, too. Of course, we’re adding more content to the reference material. For example, we’ve added information that we think you’ll find useful in Microrosoft.TeamFoundaiton.WorkItemTracking.Client Namespace ,