A: Two possible ways:
Step 1: Get the URL of the document saved in a SharePoint document library
From the project portal:
Right-click the file and select Copy Shortcut. Done.
From the Team Explorer window in Visual Studio:
Right-click the file under the Documents folder and select Properties.
The quickest way is to double-click on “Url”, then right-click the blue-marked URL on the right side and select Copy (or press Ctrl+C respectively).
Step 2: Add the link to the work item
Select Add on the work item’s Links tab:
Select the a link type of “Hyperlink”:
Paste the URL and enter a comment optionally:
Confirm with “OK”.
Pick your favorite tool for your task/job:
From Visual Studio:
From the command line:
From the web browser:
From Microsoft Office products:
From other platforms or IDEs:
From Windows Explorer:
From other products:
From Windows Taskbar:
(*) requires Team Explorer to be installed.
($) means the product is a commercial third party solution.
After uninstalling TFS 2005 (services) from a standby TFS application tier the SQL Server Reporting Services were not available, i.e. browsing http://server/reports and http://server/reportserver/ resulted in a 404 error.
Run the Reporting Services Configuration Tool and recreate both virtual directories and re-configure the identities.
(Thanks to Daniel Hackel who administers this environment.)
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:
You can manage your deployment of Microsoft Visual Studio 2005 Team Foundation Server more effectively if you create your own operations plan. As you create your plan, you should understand key elements of the architecture of Team Foundation Server and how your deployment topology affects operations. This white paper explains those elements in detail, so that you can avoid common problems with your deployment.
- Understanding Your Team Foundation Server Topology
- Managing Service Accounts
- Managing Groups, Users, and Permissions
- Managing Backup and Recovery
- Managing Configuration Information
- Monitoring Team Foundation Server
- Creating an Operations Plan
- Author Bio
- Additional Information