I have a project in Team Foundation Server. Every Time I try to either check out and check files in I get the following error.
Team Foundation Error
TF10121: The patch is not found or not supported. Type or select a different path.
I am running from the web based Version of TFS and i am using Visual Studio 2013.
Any one any idea how to fix this pop up its not allowing me to check items in.
Please check your workspace mapping, to what disk path it is mapped. Quick way to do this is to fire up VS 2013, Open "Source Control Explorer" and navigate to the SLN file. Check if it provides a path or says "Not mapped" on top. If it is mapped, try clicking on the path's link and open it.
Related
So far I was working my my project myself using Visual Studio Team Services using VS 2012, everything was good. Now I have added another user for my project and things are NOT working as I expected, below are my basic questions.
After my developer is done adding/editing files, does he needs to tell me the ChangeSet # to refer to? so I can get his Check-in's?
How Can I see What files he modified/Added? And is there a way I can get only the changes I want from the user instead of getting his/her entire changeset/files?
"Get Latest Version" does not really gets me the Latest Version of files which my developer modified.
See below answers:
After my developer is done adding/editing files, does he needs to tell me the ChangeSet # to refer to? so I can get his Check-in's?
--> He doesn't need to give you Changeset# to get latest(his check-ins). You can go to Team Explorer --> Source Control Explorer and then right click on your project and select "View History" to look at all the changes done to the project. Do you see his changes in the history? If yes then "Get Latest Version" should work. Sometimes what happens if you try to get latest version in Visual Studio Solution and if the files changed are not part of solution you won't get those files. In those cases you need to get latest from Source Control Explorer.
How Can I see What files he modified/Added? And is there a way I can get only the changes I want from the user instead of getting his/her entire changeset/files?
--> If you double click on the changeset after following the above steps to go to View History you will see all the files changed. If you want to get only few files from a check-in you will have to get the latest at file/folder level instead of getting it at project level. i.e. Find out all the files changed using above method and then go to individual files/folders in the Source Control Explorer to get latest.
I've created a new Team Project in TFS, but when I try to add my solution to it I get:
'Failed to create mapping
Cannot map server path, $/Finance/MyApp, because it is not rooted beneath a team project.'
I can't find anything on google or here that looks remotely like this problem.
I had this issue when using Microsoft's Team Foundation Service from Visual Studio 2012. I had just created the new team project via the TFS website. Although I could see my new project in the 'add solution' window, I got the error the OP reported.
I had to go into the "Team Explorer" window, then into "Connect to Team Projects" and tick the new project. Then I was able to add my solution to the team project.
Is Finance a team project for you?
If not, you can clear the mappings for the workspace or even just delete your workspace.
http://msdn.microsoft.com/en-us/library/54dkh0y3(v=VS.100).aspx
Had the same issue when upgrading project to TFS 2010 from 2008. The solution was to delete the vsssc file in the root of the project folder and re-add it
In my case I had to do Team Explorer and connect to the new project
then I had to close my solution and re-open and then the "add to source control" worked.
--Connect and check project in team explorer window
--Close solution
--Open solution
--retry adding solution to source control
I had this issue with Visual Studio Online's source control, Visual Studio would not recognize the team project even after connecting to team projects, refreshing, restarting Visual Studio. I had to use the "Open in Visual Studio" link from the project on the Visual Studio Online site and then open the solution from there.
Well, i didn't want to do anything so drastic, it turned out that one of my subfolders inside the solution i wanted to add to source control, was mapped inside a different workspace (on a different TFS server). So the solution was to connect to that other TFS server, find and delete the conflicting folder mapping inside that workspace, and try again.
I had the same problem using visual studio 2008 and TFS 2012. In my case, when I manually added the local folder to the project through the workspace mapping, the problem went away.
File -> Source Control -> WorkSpaces -> Edit
Then when I went to add the solution to source control it detected the mapping automatically.
In my case, I copied the folder from "My Documents" to c:\tfsroot where I had mapped the TFS Root. Then when I opened the solution and added it to TFS it worked.
I had the same problem. My solution in VS2017:
Open Team Explorer tab
Select Source Control Explorer
Right click on the top level folder for the project and select "Advanced/Remove Mapping"
Remove the Mapping
Right click on the top level folder for the project and select "Advanced/Map to Local Folder"
Browse to the top level folder with the source code (You may need to adjust the path you selected. It may append a folder name to the end)
Click "Map"
Answer "Yes" to Message Box "Newly mapped items will not be downloaded until you execute a get. Do you want to get $/YourFolderName now?"
That should do it!
Can anyone tell me how to revert (roll back) a checkin in TFS 2010?
You have two options for rolling back (reverting) a changeset in Team Foundation Server 2010 Version Control. First option is using the User Interface (if you have the latest version of the TFS 2010 Power Tools installed).
The other option is using the TFS 2010 version control command-line application:
tf.exe rollback
I have information about both approaches on my blog post.
For Team Foundation Server 2012, 2013, or Visual Studio Online, rollback is now built-in directly to Source Control Explorer and when you are opening a changeset's details in the Team Explorer Window. You do not need to install any release of the Power Tools for this functionality when using Visual Studio 2012 or later. There is a great MSDN article discussing details about rolling back a changeset now available here: http://msdn.microsoft.com/en-us/library/ms194956(v=vs.110).aspx
For 2010, use the rollback command from the command line. There is not integrated support in the IDE for this, as of yet.
Rollback command
Basically, the way that it works is that it creates an "anti-delta" to negate the impacted changeset. You can accomplish the same thing manually by doing a Get Specific Version, adding a space to the file so it looks like it changed, and checking it in. I still go the latter route to back out a change if I need to for a single file, as I find it quicker to do.
Without using power tools or command line:
ensure Tools->Options->Source Control->Visual Studio Team Foundation Server UNCHECK Get latest version of item on check out
View the history of project folder in Source Control Explorer and right click on the changeset to roll back to and choose Get This Version
Check out for edit on the project folder in the Source Control Explorer (this should keep your local version you just got from the history)
Check in pending changes on the project folder in the Source Control Explorer
if visual studio asks you to resolve conflicts, choose keep local and attempt check in of pending changes on the project folder in Source Control Explorer again
Rolling back changes for another user
If you are attempting to rollback changes for another user, make sure you get latest on the files you are attempting to rollback; otherwise you will see the error:
"No changes to roll back."
You can rollback a changeset (in TFS2010) through command line doing:
Open CMD or Visual Studio Command Prompt
Change directory to your workspace folder. Example: cd C:\myWorkspace
Run following tf command (where 123 is changeset number)
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\tf.exe" rollback /changeset:123 /recursive
Go to Pending Changes window to check files marked with edit,rollback and do a Check In.
Note: you must use tf.exe full path even in Visual Studio Command Prompt to avoid "Unable to determine the workspace" error. More info here
Rollback reference (TFS 2010)
https://msdn.microsoft.com/en-us/library/dd380776(v=vs.100).aspx
right click file in Visual Studio and Source Control/View History
then select last changeset, right click and click Rollback
After rollback done, you should check in again.
There is no undo option in TFS (up untill 2008, I haven't used 2010 yet).
There are some command line power tools you can use to rollback changes that may help:
http://msdn.microsoft.com/en-us/library/ms194956%28VS.80%29.aspx
HTH
I don't know what I've done, but on my TFS source control explorer I have "No commands available" on the context menu! (Panic is setting in)
From the Team Explorer I can see that am a member of Team Foundation Administrators, and I'm a member of the team project administrators as well.
What would be causing TFS to give "no commands available" on the pop-up context menu?
Additional info:
I can get to the source control explorer and with additional commands from another machine, so perhaps it's something pooched on my setup (although it was working an hour ago!)
In Visual Studio, go to Tools > Options...
Click "Source Control" in the tree
Select "Visual Studio Team Foundation Server" as the current source control plug-in.
If this option is not available, ensure that you have Team Foundation Client installed.
You need to checkout (Mapping is not enough for Moving and Renaming - for that you MUST check-out) those files/folders to your local disk, before you get the context menu on right-click that you miss.
I had same problem and from the MSDN official page I was not too much wiser :)
Anyway, I wonder what is the good reason, for which you can not move files in TFS server repository without checking-out those items to my disk. In SVN this is no problem. (And there is even no path mapping in SVN - just CheckOut :)
We're using Visual Studio 2008/TFS 2008.
We have a small team of developers and for some reason, periodically, when any of us "Get Latest," one of our paths remaps to a different path on it's own. This causes the "Get Latest" to start deleting files, because the path has changed. It's the same path every time that gets remapped to the wrong path.
Where are workspace definitions stored?
Is there something we may have checked into TFS that's causing this?
I have had this happen when I get while opening a solution. If the solution contains relative paths to other projects not under it's folder, that are mapped differently in your workspace, the GET will tell me it's remapping to account for it. Problem is the decisions that it makes are completely wrong.
The only way around it was to ensure that all developers use the same structure that sourcec control uses and havev that represented in each workspace.
Getting there was a pain though. basicly everyone had to delete all local copies of all files, redo workspace, CHOOSE NO TO 'GET' WHEN WORKSPACE CHANGED, close VS, open, GET LATEST.
The reason for that was if copies of projects exsisted local, even if those projects were NOT open, the GET would still be wrong. This was frustrating, because when checking for differences in those projects with latest there was no change, but when opening the solution that contained that project, dll references in that project would auto change. At that moment, no changes are pending on ANY file. But after building the changes would persist and cause the next get to be off again...
I'm sure this is all wrong, but that's what happened to us this week.
This is not normal behavior - sounds like something is going funny. Just wanted to check - all you are doing is simple get's from Source Control explorer correct? Also - all of you are on different machines? (I.e. you are not sharing a virtual PC image or anything where multiple machines have the same name)
One think I would check is to go to File, Source Control, Manage Workspaces and look at your working folder mappings both before and after the get and see if anything is changing. It shouldn't - if it does this might give us a clue as to what is happening.
You can also try clearing your workspace cache and remap it:
SET AppDataTF=%USERPROFILE%\Local Settings\Application Data\Microsoft\Team Foundation
SET AppDataVS=%APPDATA%\Microsoft\VisualStudio
IF EXIST "%AppDataTF%\1.0\Cache" rd /s /q "%AppDataTF%\1.0\Cache" > NUL
IF EXIST "%AppDataTF%\2.0\Cache" rd /s /q "%AppDataTF%\2.0\Cache" > NUL
IF EXIST "%AppDataVS%\8.0\Team Explorer" rd /s /q "%AppDataVS%\8.0\Team Explorer" > NUL
IF EXIST "%AppDataVS%\9.0\Team Explorer" rd /s /q "%AppDataVS%\9.0\Team Explorer" > NUL
Ok i got it. Here is the solution.
First of all install Visual Studio 2008 SP1.(i suppose you have VS 2008 and Team Explorer already installed).
Now launch Visual Studio 2008, Goto Source Control and delete workspace.
Create a new workspace and make a source control folder to local folder mapping.
Click Ok. When it asks "Workspace has been modified, you you want to get latest", Select NO.
Now Close Visual Studio 2008.
Reopen Visual Studio 2008 and go to source control and Get Specific (with both check boxes checked for overwriting files).
If you have a asp.net web based solution, now is the time to create application pool, configure website in IIS, set proper authentication and authorization. Otherwise its optional!
Now goto the appropriate folder in source control and double click the solution file. You may also open the solution by double clicking the solution file in your local folder but i find it easier to open the solution from source control.
Doing the above step, if your website is configured, Visual Studio 2008 will automatically detect your website that you had setup and prompt you to confirm it. Click ok.
It will contact the source control server to see if synchronization is necessary or not. If you have a number of projects in your solution, you will observe the file-get progress bar quickly blink across your screen and your solution will be setup in minutes.
The real problem is of Visual Studio 2008 Service Pack 1. Without which TFS mapping gets corrupted. IF SP1 is installed and the above guide is followed there will be no problem.
The Workspace definitions are stored on the server.
If you go to the command line and type "tf workspace", you will see the definition of your workspace.