We tend to use a virtual machine per external client so that we can keep things nicely separated. We can then easily add people to a project by giving them a copy of the virtual hard disk and they can be up and running in minutes (once they’ve renamed the guest machine name to avoid IP conflicts!) That worked fine until we started using TFS, where it would moan that the workspace doesn’t exist because its now a different user accessing TFS. After some digging i found the answer was to edit the following file: C:\Documents and Settings\[USER NAME]\Local Settings\Application Data\M... [More]

When trying to connect to TFS 2008 on VS 2008, I had this error: The path xxx is already mapped in workspace xxx It turns out that when using my VPC, it was cloned incorrectly. Someone else had created a workspace using their credentials, cloned the VPC for my use and then when I logged on using the same account name, I got this error message. The way to allow you to continue is to close VS 2008 and then rename the settings file with a .bak extension located at: C:\Documents And Settings\<current user>\Local Settings\Application Data\Microsoft\Team Foundation\2.0\Cache\VersionControl.... [More]

We’ve recently been looking at importing Microsoft Project tasks into TFS so that the developers can see their tasks inside visual studio. However the first snag was that TFS work items aren’t able to support more than one resource being assigned to them, a problem when your Project Manager has allocated more than one developer to do the same thing! Also some of the tasks in the project plan are assigned to the client, E.g. ‘Sign Off Wireframes’ and by default TFS will only allow you to assign work items to valid users than exist in your companies Active Directory. I got round the multiple r... [More]