February 2008 - Posts
From the contents:
- Team Foundation Server Extensibility
- Team Foundation Server SDK Architecture
- How to: Run Team Foundation Server SDK Samples
- Team Foundation Core Services
- Work Item Tracking Extensibility
- Source Control Extensibility
- Data Warehouse Extensibility
- Reference for Team Foundation Server SDK
Code churn  in TFS 2005 and TFS 2008 is calculated using a very simple algorithm: inserted + changed + deleted lines .
This is done independently of the contents of the line, which means that everything - incl. comments, blank lines, etc. - is counted.
Due to a lot of requests about this pretty common problem.
Steps you did:
- You browsed for a web part:
- You selected one and hit "Add":
- You got the error message: "An unexpected error occurred."
This is a know issue with WSS 2.0 and a hot fix  can be requested at Microsoft which corrects this behavior.
I tried this with various customers and we could then successfully add new web parts after applying it.
They are two major problems when looking into the history with regard to links.
1. No clue what has changed:
If you remove an attachment and add a completely different one the history will indicate that there was a change (revision gets in incremented by 1), but it won't tell you what has changed since TFS only tracks the numbers (e.g. number of external links).
2. Work Item links are only reflected in history on one side:
You have two work items: item 52 and item 53.
You decide to link item 53 with item 52.
Both items show the work item link under their "Links" tab.
Item 53 shows the new link in the history:
But the history of Item 52 shows no changes at all:
Since Team Foundation Server 2008 was released end of November 2007 the early adopters which for some reasons have not obtained a product key yet are facing the problem of expiring trial licenses on their TFS servers.
I definitely recommend to find out when your TFS trial expires. You can use the Version Detector Tool , which Brian Harry  blogged about.
If you have trouble getting a product key in time:
- From ten days before it expires you can extend the trial period for 30 additional days (using the tool mentioned above).
- If that's not enough contact Microsoft to get additional 30 days.
Eventually people will check for the expiration date before they actually learn it the "hard way"...
So: don't be a fool, use the tool!