DeleteWorkspaceTask fails on 2008 build machine after installing Visual Studio 2010 RC - by dzimmy

Status : 


Sign in
to vote
ID 538958 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 3/4/2010 5:53:07 AM
Access Restriction Public


Our 2008 builds are failing after installing Visual Studio 2010.  First DeleteWorkspaceTask is not able to delete existing workspaces.  Then after manually deleting and re-running, we ran into some other pre-reported issues, e.g. GenCheckinNotesUpdateWorkItems fails because AssociatedChangesets parameter is not supported.  Why would a 2010 studio (not even build) install step on the 2008 build mechanism?  Our work-around right now is to install 2010 build items on a box that doesn't have 2008 team build. 
Sign in to post a comment.
Posted by Microsoft on 3/5/2010 at 11:26 AM
Thanks for reporting this issue. The problem is that in 2008 the workspace name needed to be unique to the machine and the build definition, while in 2010 it needs to be unique to the machine and the build definition *and* the build agent (since there can be more than one agent per build machine in 2010). As such, the name of the workspace created by the 2010 targets file is slightly different from the one that was created by the 2008 targets file, leading to the issue you have seen.

You can work around this issue by either (a) deleting the existing workspace - thereafter the workspace used for the build will have the new name, or (b) manually set the WorkspaceName property back to its old value in your TfsBuild.proj file. Something like:


...should do the trick.

Note that this issue only occurs on build machines which are upgraded from 2008 to 2010 when they run builds for build definitions they had already run builds for. That is, it will not occur on new 2010 build machines, and it will not occur for new build definitions even on upgraded machines.
Posted by Microsoft on 3/4/2010 at 7:03 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(