To remove an existing Work Item Type (WIT) you must modify the Category template to exclude the WIT in order to avoid receiving an error when attempting to delete.

Error

Unable to destroy work item type Test Case

TF237055: You cannot destroy a work item type that is being used.

Verify that the work item type is not being used in any categories.

Operation failed.

Remove the WIT from the Categories XML file.

1. Open the Visual Studio Command Prompt (2010) by browsing to the location below or set the environment via the command prompt by executing the Batch file (VS2010) :
• “C:\Program Files\Microsoft Visual Studio 10.0\VC\vcvarsall.bat” or Locating the VS Prompt on your Programs Menu
2. Export the categories using the [witadmin] command:
• witadmin exportcategories /collection:http://AdventureWorksServer:8080/tfs/defaultcollection /p:AdventureWorks /f:c:\mycategories.xml
3. Open the exported categories XML from the location listed for /f: from above using notepad, remove the unwanted work item type by deleting the CATEGORY tag and it’s contents. Then save your changes.

• <CATEGORY refname=”Microsoft.TestCaseCategory” name=”Test Case Category”><DEFAULTWORKITEMTYPE name=”Test Case” /></CATEGORY>

4. Import the modified category file using the import witadmin importimportcategories command.

• witadmin importcategories /collection:http://AdventureWorksServer:8080/tfs/defaultcollection /p:AdventureWorks /f:c:\mycategories.xml

Deleting the unwanted work item type.

1. Executed the witadmin destroywitd command to PERMANENTLY delete the work item type and ALL work items of that type. This command is NOT reversible once executed.
• witadmin destroywitd /collection:http://AdventureWorksServer:8080/tfs/defaultcollection /p:AdventureWorks /n:Test Case
2. Verify in Team Explorer that the work item type is no longer available.

For more information on managing Work Item types visit the MSDN Site. http://msdn.microsoft.com/en-us/library/dd312129.aspx

This issue occurs when using Visual Studio 2005 or VS 2008 without the compatibility update installed.  If you 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

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

When making an attempt to add a new client to WHMCS and assign a domain name that was registered before with my existing ENOM account I would receive Registar Errors. When the cron job would run to synch up the expiration date it would return the first error below. Here is the steps I took to resolve the issue.

Resolutions:

First Error: Registrar Error Domain name not found
Resolution:
1. WHMCS Admin
2. Servers
3. Updated the IP of WHM to the new IP. (I was assigned a new IP for SSL and did not update WHMCS

Second Error: Registrar Error Invalid client IP: 22.22.222.222
Resolution:
1.Opened a ticket with Enom API Support to update their end with my new IP address.

Steps Taken Once The Above Was Resolved
http://wiki.whmcs.com/Importing_Data#Manual_Domain_Only_Entry

Manual Domain Only Entry

To add a domain on it’s own without a product, follow the steps below:

1. On the client summary page, click the “Add New Order” link in the Actions panel
2. The client will be preselected, so you should fill out the rest of the form – begin by choosing the payment gateway you want the client to pay with
3. Leave the Product/Service dropdown menu set at None
4. Leave the Billing Cycle dropdown menu set at Monthly
5. Enter the domain in the Domain text field and select Register as the Domain Registration Option (even though you aren’t intending to register it today)
6. Choose the number of years you next want the client to be invoiced for at the time of renewal and tick any addons the user has for their domain
7. Ensure both tick boxes for sending an order confirmation and generating an invoice are unchecked so the user is not emailed about the order you are adding
8. Finally, set the Order Status dropdown to Active and then click the submit button to add the order to WHMCS
9. You will now been shown the order screen summarising the details of the order you just added
10. Now as the final step, you must go to the domain’s information page to enter the correct next due and expiry dates aswell as selecting the registrar the domain is registered with if using one of the built in registrars. To do this, from the order screen, click on the link in the Type column of the items ordered – this will take you straight to the details screen.

You have now finished adding your client. By following the steps above, your client will have not been notified that you’ve added them and will now be invoiced by WHMCS prior to the next due date for the items you have added to their account.

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

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.