Team Foundation Server - Solution Bindings Gone Missing - visual-studio

I got this problem with TFS, I connected to the wrong network and tried to open a solution and it gave the error: "cannot connect to tfs". Fine, I closed the solution, and I switched to the correct network and now it says "the solution appears to be under source control but the bindings are missing bla bla."
I check the Team Explorer tab, and it shows that it's connected, but the solution, the projects lost interest in tfs somehow.
When I say "Change Source Control" and try to "Bind" all of the projects, it asks to check out every project, but I don't want to deal with conflicts now, I need my currently checked-out files.
did anyone face this problem and solve it?

Ok, I think I've found a solution:
Right-click on solution and click "Add Solution To Source Control". Then it says something like "Are you sure? This project already seems to be under some source control", click "Ignore All" for everything that pops up. And viola, your bindings are magically back in order. I really don't know why, or how. it just happened.
But this operation might checkout your solution file if it's not checked out already.

Related

When opening a script from Unity, Visual Studio opens the wrong solution

I have multiple Unity projects on this PC, however this problem only affects one of them, the one which is connected to Plastic SCM named "My Daughter's Adventure". Please ignore the name :). If I try to open a c# script from Unity, it opens it like this. However, the correct .sln file does indeed exist in the correct folder, shown here.
If I try to open one of my "offline" projects, everything works fine. Image here.
Now, I can open the .sln file manually and then open the script file from Unity. That brings back Intelisense and that little code dropdown menu, but this method has been kind of bipolar. Sometimes everything works fine, otherwise I get errors in Unity regarding the name of the script that doesn't correspond with anything and it asks me fix "compile errors" even if there aren't any.
Do note that I tried everything, at least what I could find online in terms of fixing this, including the preference settings in Unity. I'm also kinda new to Unity and Visual Studio. It took me 3 hours just to identify the problem and made an account just for this problem. Can anyone help me?

Remove TFS Bindings without a hack

I have a 2013 Visual Studio Web Project which was in source control. It has been detached for some time and now I want to move it to a completely new TFS server but when I do it errors and complains expecting certain folders to exist. I think this is due to the TFS bindings.
Now I have seen lots of posts about how to edit the solution file to remove the bindings, plus a few other steps but I'm wondering if there is a menu item which you can click to remove the bindings so I can point at a different TFS server? I am hoping I don't need to edit solution file.
I am not simply being lazy - but I want a defacto way of doing this correctly in one go, not hack here and hack there. Hacking a solution file from someone's advice is not the same as clicking a 'Microsoft' menu item.
Quite easy, you just need to follow my steps and you will get it worked.
Open your solution, for now its under source control with your old
TFS server.
Move to File -> Source Control -> Change Source Control , on the
pop-up window click the unbind, you can unbind all of the
solution or a specific project. Will get a below screenshot.
You can check the solution in solution explorer, there is no lock
icon which means not in source control any more.
However, this isn't over. Since your solution file is still in the
workspace which associate with the old TFS server. So if you want to
add the solution to new source control right now, you will get an
error:
" The item 'ConsoleApplication1.sln' is already under source control
at the selected location xxx"....
You have to copy this solution to a different place out of your
workspace. And change the connection of TFS to the new TFS
server(which you want to add source control with).
Finally, open the solution from local folder(new copied). Right
click the solution in solution explorer select "Add solution to
source control" and choose the location you want add to.

Blue question mark on files in solution explorer

I often get blue question marks on files in my VS2012 Solution Explorer when opening a solution bound to Perforce through P4VS.
Looks like something is having trouble to "synchronize" with the depot/workspace/whatnot. Hitting "Refresh View" always solves the issue but I'm growing tired on doing this everyday:
This is my VS version:
Microsoft Visual Studio Professional 2012
Version 11.0.61030.00 Update 4
And P4VS:
2014.1.85.4506
This is persistent across P4VS versions for a few months now, and seems to be affecting sometimes individual files, sometimes entire projects, with no apparent pattern.
How can I diagnose what's going wrong, be it a server issue, a VS issue, a workspace issue?... The Perforce Source Control output shows nothing special.
Actually it's not entire folders, it's entire projects. It appears that even if refreshing a project "fixes" the issue for one run, re-opening the solution brings it back. Whereas I think that for individual files, refreshing them solves the issue once and for all. I'll play with it a bit more to confirm that.
To help diagnose what is going wrong you should probably turn on logging, and check the preferences that will show everything in the output window. For the P4VS log, go to:
Tools- > Options -> Source Control -> Perforce - Logging
(This is not the same thing as the Visual Studio Activity log.)
There could be a possibility that you are getting disconnected and refresh reconnects you. I am not sure if you have your connection set to use solution-specific settings, since you did not mention the connection dialog coming up.
This "solved" the issue for me, at least for the entire projects that went blue-question-marked:
1) Tools > Options
2) Source Control
3) Perforce - General
4) Tick the option "Treat Solution/Project as directory when
selected"
Not sure why but that's one less annoyance for me every day. Thanks to Perforce support for suggesting that.
The file is probably not marked for version control. I noticed this icon in one file and opened Perforce to check. For whatever reason, this file was not marked for add in Perforce. After marking the file for add and submitting, the blue question mark went away.

Visual Studio loses bindings to TFS suddenly

Why would my VS solution lose its TFS bindings suddenly? I have been working on a project for six months and this never happened. As soon as I opened a VS project/solution, I could check in/out, view history by right clicking on any given file. But suddenly, I dont see those options to checkin checkout etc any more when I right click on a file in VS studio solution explorer.
The team explorer window still brings up the source folder structure and I can get latest or get specific from there but did any one see this kind of behavior? Please let me know what I can do to avoid these situations in future.
Did you lose connection to the TFS server any time recently? I've had this happen in the past on unreliable network connections when working via TFS remotely. The solution and all projects therein would "go offline" and would appear to lose their bindings. This made it particularly unintuitive when the connection was re-established because changes made while "offline" weren't always found.
If you right-click on the solution or the projects, is there an option to "go online"? You might check the various menus for such an option as well.
Did you move the source files to a different location on your harddrive, or change your workspace mappings?
Try opening the solution/project by double-clicking the .sln file in Source Control Explorer instead of opening it from windows explorer.
You can also try bringing up the Bindings dialog by going File -> Source Control -> Change Source Control
I recently had a very similar experience. I had made several changes which I thought may have influenced my connection resilience. After reversing out of 2 of them and the problem persisted, I finally clocked what it was.
One of the new extensions I am using is NuGet (http://nuget.codeplex.com/). Every time I attempt to add a library my TFS connection fails and is unrecoverable till a restart of VS 2010.
See: http://nuget.codeplex.com/workitem/725
There is a work around that has been reported and working which may help you even if this is not your problem.
see http://blog.rthand.com/post/2011/08/26/Fixing-combination-of-NuGet-and-Team-Foundation-in-workgroup-configuration-401-Unauthorized.aspx
Happened to me also. I was removing a whole bunch of mappings for old releases under the local workspace. It was taking over 40 minutes so I killed it. The mapping has been removed to the older branches but the branch left behind had been disconnected from TFS.

Spurious dialogs "Project exists, overwrite from source control" when opening solution

Just recently, when I open a solution in VS2010, I get modal dialog boxes in the form
"Project c:\XXXX\YYY\ZZZZ.csproj, which
you are getting from the source
control store, already exists. Would
you like to overwrite it with the
store version, or leave your local
copy?"
With the options Overwrite, Overwrite All, Leave and Help. I get one of these dialog boxes per project in the solution, unless I click Overwrite All. Either of the Overwrite options appears to do a get for every file in the project(s), which as you can imagine is time consuming for a large solution. And clicking Leave for every project in a large solution is also time consuming.
The obvious cause is the option Source Control -> Environment -> Get everything when a solution or project is opened, however this is not turned on. I tried turning the option on and then off again, in case something was wrong with the option setting, but this did not solve the issue.
I've tried a few searches for this issue, but couldn't find anyone else suffering it.
Any help solving this would be appreciated.
I've also asked this question on Super User
Clear your Visual Studio Cache Settings and then try again.

Resources