Koen about .Net

October 29, 2009

Local folder already mapped in workspace

Filed under: Development — Tags: , , , — koenwillemse @ 11:53

I’ve got a small server at home where I also run TFS on for my personal projects and for playing around with it to try some stuff.

Since TFS 2010 Beta 2 is available I wanted to work with VS2010 and TFS 2010. As I’m just a geek who wants to play around with it at home, I didn’t plan how to do this change etc. Because I didn’t care much about the history in source control, I decided to simply reinstall my server (I was already planning to do this as I wanted to use SQL Server 2008).

All went pretty well when installing and configuring. But then yesterday I wanted to add all the source I had on my local machine to the source control. And then the probleem started.
I got the message stating that I already had a workspace mapping for the local directory. WOOPS…. And I couldn’t connect to my old TFS server anymore because I destroyed that completely :).
So I hadn’t got a clue what to do, because for as far as I know, the workspace mappings were registered at the server, not locally. I already removed the source control bindings from the solution, but that was not enough. Still getting the error.
It took me quite some time to find that the workspace mappings are also cached on your local machine. I finally found the mapping mentioned in the folder C:\Users\[USER]\AppData\Local\Microsoft\Team Foundation\2.0\Cache\versioncontrol.config. I deleted it from there and I could finally add my source to source control again.

Lesson learned: Think twice before doing a format on my server and try to do some planning / impact analysis before throwing things away, even when I do it on my ‘playing around environment’.

Edit: this is the location on a Windows XP machine: C:\Documents and Settings\[USER]\Local Settings\Application Data\Microsoft\Team Foundation\2.0\Cache


July 14, 2009

TFS2008 build fail because data.coverage is being used

Filed under: Development — Tags: , — koenwillemse @ 09:21

Today we ran into a strange problem. The nightly build had failed when trying to empy the working folder on the build server with a message like “cannot remove file ‘data.coverage’ because it is being used by another process”.

Very strange because nothing special was going on on the build server. For some reason the process VSPerfMon.exe had continued running. I killed the process and started the build again. Now the build runs again and didn’t have the problem anymore.
Strange… Looks like the test host just crashed or something like that. No idea (yet) why that happend. I’ll update the post if I find out why this happened.

If you have the same problem, just kill the VSPerfMon process and clean the directory. Probably the build will run again then.

Create a free website or blog at WordPress.com.

%d bloggers like this: