TfsDeleteProject /server:tfs-server-name "Project Name" /force

This appeared to work except for the exception we got from SharePoint Services:

Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.

Fair enough, it seemed we had a problem that the team portal had broken somehow, but this was preventing us from re-creating the team project once more because the wizard was unable to create the site over the top of this one.

Unfortunately when attempting to browse to the site, we got a “400 Bad Request” error, and when attempting to delete the site using the Central Administration, we couldn’t select it from the list. The site truly seemed to be a ghost (or relic) of what was once a great site.

Fortunately, after my colleague found this article explaining how to delete orphaned sites from WSS, we were able to solve the whole problem using step 2: removing the WSS_Content database from WSS, and re-adding it.

This idiotic process of deleting a team project certainly needs cleaning up in the next version, but for now, I hope this helps anyone else with this problem.

I have used Visual Studio .NET 2003 Professional, Visual Studio 2005 Professional and Visual Studio 2008 Professional, without much knowledge of there ever being a set of versions designed for teams, known as Team System. Today I have decided to make use of our “workgroup edition” license of Team Foundation Server, with Visual Studio Team System 2008 Developer Edition as my choice of client. The benefits seem to vary between editions of the client, but suffice to say that when looking at the comparison site below, the developer edition is packed with many more features that the professional edition.

Compare your versions here: Visual Studio 2008 Product Comparison