TFS Solution Explorer missing checkout icon - tfs

I recently upgraded TFS server from 2013 to 2018.2
Developer with VS2013 can't check-out file from Solution Explorer, but this developer can check-out the same file from Source Control Explorer.
What is the reason and how to fix?
Log window: Value cannot be null. Parameter name: workspace
Thanks

I saw that the problem was with the workspace, as I created new workspace (on the same PC) and I could check-out the file from Solution Explorer
Thanks!

Related

Open in Windows Explorer option missing in VS2015

So it appears that TFS Source Control Explorer in Visual Studio 2015 is missing an option available in Visual Studio 2013 - "Open in Windows Explorer" when right-clicking a folder. I've looked for this option in Tools > Options without success. Has anyone found a way to get this option back? (yes, I'm aware I can right-click a folder in Solution Explorer, but sometimes you're browsing a repository and it's a huge timesaver to have the option there).
This option is from Windows Shell Extensions of TFS Power Tools, so you need to install TFS Power Tools, then you'll see this option.

Configure Visual Studio 2013 to use TFS and not GIT

I have been using TFS quite happily the last few months, and all of a sudden my project is now using GIT.
I think it was after I installed the Eclips TFS plugin for android development.
How can I change it back to use TFS as my source control.
When I click on Team Explorer now it is git.
IIRC see Tools / Options / Version control and select the default version control plugin.

Error: The imported project "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.Cpp.Default.props" was not found

I have migrated a VS2008 solution to VS2013. My solution contains VC++ projets.
I have set the tools platform to v120_xp for each project
My solution compile on my computer and compile on my builds server in VS2013
My builds server is a Windows2008 R2 with VS2008, VS2010 and VS2013 and a build controler of TeamFoundationServer 2010.
When i launch the build with the build controller, the build fails with :
The imported project "C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.Cpp.Default.props" was
not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.
In the V110 directory this file doesn't exist but it exist in the V120 directory.
I have checked the registry :
HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersion\12.0
the VCTargetPath are corrects
Have you an idea to help me?
I have edited the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSBuild\ToolsVersions\12.0\11.0
and
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\12.0\11.0
to use the V120 directory
Now my server build the solution, but i don't understand why MSBuild use the key
ToolsVersions\12.0\11.0 and not the key ToolsVersions\12.0\12.0
Parhaps it's due to the v120_xp platform toolset
The true answer is that MSBuild subtracts 1 from the .sln Visual Studio Version. Since you do not have VS 2012 install or you have not installed it, the v11.0 folder is not found. It is all explained by Sayed Ibrahim Hashimi:
http://sedodream.com/PermaLink%2cguid%2ca5894bad-f2a1-441a-a5b2-74f16c6cf8aa.aspx
I came across the same problem in 2015 though, with Windows 10 and Visual Studio 2015 RC (fresh install)
To correct the issue I tried several solutions based on my research ie installing "VS Windows SDK" which didn't do anything different to resolve my problem, I then on another recommendation installed GitHub in order to download MSBuild which is now excluded from VS, I ultimately downloaded and installed "VS Tools for Windows 10" this didn't give me the same error in the end, without having to change registry keys
Installing VS 2012 on your build server should create the necessary targets files for you.
I was able to get past this by changing $(VCTargetsPath) to $(VCTargetsPath12) in the project file.
This feels like a temporary workaround rather than a permanent solution, since once we move to the next version of Visual Studio we'll have to find all the references to $(VCTargetsPath12) and replace with the new target path.

visual studio 2012 ,tfs project loading failed

My admin of the TFS rename the project name and when i get the latest version all other projects are loaded to my local visual studio but the project which have been renamed is not loading . I tried to delete the solution from the local mapped path and then got again latest version but still the problem is same and its give me a message that the Project file .csproj has been moved ,rename or not in you computer. I also tried to delete the .SUO file and get specific and latest version restart visual studio added the existing project to solution . I spent many days to resolve the issue but I am not able to do so , can any one help me in this Problem ,
Check the solution file when it comes our of TFS. I have had an issue similar to this, and I could see the correct files comin out of TFS into my local workspace, but the minute I loaded it it VS, all of the old code came back.
Eventually I discovered the solution file still referenced my old code, which caused it to be loaded in from the TFS profile.
See if the admin physically renamed the files in TFS but didnt change the details in the soluton and project files.

why is my Local Path mapping is a not a link in my Team Explorer Source Control window but my desk mates have there hyperlink

i have visual studio 2008 sp1 installed but still my team explorer dosent shows the hyper link of the local path
If you installed Team Explorer after you installed VS SP1 then you need to re-run the SP1 installer in order to bring the Team Explorer bits up to date.
This suggests that the install has either gone wrong or another update has interfered with your Visual Studio.
Can you try applying the service pack again?

Resources