Category archive - Reference

TF31002 : Unable to connect to this Team Foundation Server

Connecting to TFS 2010 from Visual Studio 2005 or 2008 

This issue occurs when using Visual Studio 2005 or VS 2008 without the compatibility update installed.  If you have already installed the compatibility update then its possible that the URL used is incorrect. Verify that the URL for TFS meets the following format http://YOURTFS:8080/tfs  . If you have not installed the update you will need to do so in the specific order below.

ERROR: TF31002: Unable to connect to this Team Foundation Server: tfs2010.

Visual Studio 2005 to TFS 2010

 The process must be completed in the exact order to work.  

1. Visual Studio 2005
2. Install TFS Team Explorer 2005
3. Install Visual Studio 2005 Team Suite SP1
4. Install Visual Studio Team System 2005 Service Pack 1 Forward Compatibility Update for Team Foundation Server 2010 (Installer)

Visual Studio 2005
On the Visual Studio Toolbar go to Tools and select Connect to Team Foundation Server

Select Servers

Select Add and enter the server details  http://tfs2010:8080/tfs

*The Connection Details on the screen should gray out after entereing the URL. If this is not the case, then the “Forward Compatibility Service Paack” has not been installed or the order it was intalled is incorrect. *

Connection Completed

Visual Studio Team System 2005 Team Explorer

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=7203

 Microsoft® Visual Studio® 2005 Team Suite Service Pack 1 http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5553

 Visual Studio Team System 2005 Service Pack 1 Forward Compatibility Update for Team Foundation Server 2010  http://www.microsoft.com/download/en/details.aspx?id=3263

Connecting to TFS 2010 from Visual Studio 2008

Visual Studio 2008 (The Same process as above with the following software below)

1. Visual Studio 2008
2. TFS Team Explorer 2008
3. Visual Studio 2008 SP1 (installer only) (ISO – Full download)
4. Visual Studio Team System 2008 Service Pack 1 Forward Compatibility Update for Team Foundation Server 2010

AGILE Software Development and TFS 2010

While researching ways to use TFS 2010 with the AGILE method of Software Development, I created a quick but efficient outline that is useful when proposing the process for developer and business use. I also added a few links that could assist new users to Team Foundation Server, with details on how to complete certain task within TFS. It would be great to read suggestions from others that may be using TFS in a different manner to broaden my knowledge base.

The Development outline while working with TFS 2010 is as follows.

1. User Stories are entered in TFS with Estimates.
2. Tasks are created and linked to the User Stories.
3. Test Cases are created in TFS and linked to User Stories.
4. Bugs are filed and linked to the User Story.
5. Once all Tasks,Test Cases, and Bugs are completed the User Stories are mark as resolved.
6. Reports are created to ensure all items are resolved and the Project is complete before release.

Work Items and Workflow (Agile)

• Defining User Stories, Tasks, and Other Work Items
• Creating a User Story, a Task, or Another Type of Work Item
• Creating Many User Stories, Tasks, or Other Work Items at One Time
• Creating a Work Item that Automatically Links to Another Work Item
• Creating Test Cases and Test Plans By Using Test and Lab Manager
• Opening and Tracking Bugs By Using Test Runner and Test and Lab Manager
• Viewing Work Items Assigned to You
• Customizing Work Item Types and Related Tasks

http://msdn.microsoft.com/en-us/library/dd997897(v=VS.100).aspx#CreatingManyWorkItems

Working with User Stories

• Defining a User Story
• Adding and Linking Tasks to a User Story
• Adding and Linking Test Cases to a User Story
• Adding a Bug to a User Story
• Adding an Issue to a User Story
• Adding Details, Attachments, or Hyperlinks to a User Stories
• Resolving and Closing a User Story

http://msdn.microsoft.com/en-us/library/dd380634(VS.100).aspx#LinkBug

Working with Tasks

• Defining a Task
• Linking a Task to a User Story
• Linking a Task to a Bug
• Adding Details, Attachments, or Hyperlinks to a Task
• Closing Completed Tasks

http://msdn.microsoft.com/en-us/library/dd380700(v=VS.100).aspx

Complete Process with Details on All Reports

http://msdn.microsoft.com/en-us/library/dd997796(v=VS.100).aspx#TrackTheProject

Product Planning Workbook (Reports)

http://msdn.microsoft.com/en-us/library/dd380682(v=VS.100).aspx

MSF for Agile Software Development v5.0

http://msdn.microsoft.com/en-us/library/dd380647(VS.100).aspx

Two Pc’s, Two Monitors, One Mouse, One Keyboard, One Input Director!

I have always had a rough time swapping between keyboards for my laptop and desktop until now. Thanks to Input Director (http://www.inputdirector.com/)  I can use one keyboard and one mouse to control both. No extra Hardware needed! The mouse will scroll through all three of my monitors and I really love the cursor wraparound feature. Ok enough with the infomercial check it out for your self if you are interested! It’s FREE!

Input Director

Input Director is a Windows application that lets you control multiple Windows systems using the keyboard/mouse attached to one computer. It is designed for folks who have two (or more) computers set up at home and find themselves regularly sliding from one system to the other (and wearing out the carpet in the process!). With Input Director, you can share a single keyboard/mouse across a set of systems. You switch which system receives the input either by hotkey or by moving the cursor so that it transitions from one screen to the other (in a very similar fashion to a multi-monitor setup). The idea being that you can position the monitors from two or more systems in a row and use a shared keyboard/mouse to control all of them.

Input Director also supports a “shared” clipboard, in which you can copy data onto the clipboard on one system, transition across to another and paste.

Input Director requires Windows 2000 (Service Pack 4), Windows XP (Service Pack 2), Windows 2003 or Windows Vista. The systems must be networked.