No workspace exists for the given Team Project
I get the above error when trying to set up a new Build Type for a Team Project I just created.
I was able to successfully create the project and the corresponding source control branch, as well as add a solution to it (which successfully was added to SCC also).
All of the workspace mappings between my local folders and SCC seem to be valid and working. It does not seem that the workspaces it is looking for are the same workspaces as these?
I suspect that this problem may stem from the fact that I had previously created a project under the same name and deleted it using DeleteTeamProject.exe (successfully, or so I thought).
Is there any way for me to fix this?
[676 byte] By [
chooch] at [2007-12-16]
additional info: its not just the project that I am reusing the name for that causes this error - its ANY new project.
I am unable to create a new Build Types for any new project I create.
Please make sure that the workspace has a mapping to the Team Project you are trying to create a build type for. We have issues around multi rooted workspaces in Beta2, so please make sure that all local folder mappings have the same root, for e.g., the build type creation wizard does recognize the workspace if it contains mappings to different local folders say ‘c:\documents and settings\foobar1’ and ‘d:\foobar2’
To make quick progress, you may want to create a new workspace altogether as follows:
- Open VS command prompt
- Run 'h workspace /new /s:<TFSServerName>'
- Create a mapping between $/<TeamProjectName> and a local folder in the opened dialog and say OK
You can now use this workspace to create the build type.
Thank you,
Nagaraju Palla,
Visual Studio Team System | Team Build
This post is provided as-is and without warranty
I have created a complete new workspace and defined a directory for the root of the Source-Control Container ($/) but I still get this error message.
I created the workspace using File > Source Control > Workspaces..., though! I _did_ remove all local projects and used the source control explorer to retrieve a new version into the new workspace.
For some projects, I am able to add a new build type, but not for others?!?
Could there be another cause?
FYI: I have found a post which talks about a limitation which causes this:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=4442In short: temporarely remove all other project paths from your workspace and keep only one for the project you want to create a build type for. After you created the type, you can restore the mapping. This limitation is fixed post-SP2.
