Menu
I recently had a problem in which I could not add a new project to an existing solution which was bound to TFS source control. The only option I would get when I right-clicked on the new project was Source Control -> Add Solution to Source Control, which looked something like this:
Tfs Visual Studio Tutorial
Fixed in: visual studio 2019 version 16.7 preview 2 visual studio 2019 version 16.0 preview windows 10.0 gitux git-ux top git suggestions Jonathan Ou-yang reported Mar 20, 2019 at 06:20 AM. Alternative Version Control options in Visual Studio for Mac. For the best version control experience on macOS, we recommend using Git instead of Team Foundation Version Control (TFVC). Git is supported in Visual Studio for Mac and is the default option for repositories hosted in Team Foundation Server (TFS)/Azure DevOps. Visual Studio Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. It comes with built-in support for JavaScript, TypeScript and Node.js and has a rich ecosystem of extensions for other languages (such as C, C#, Java, Python, PHP, Go) and runtimes (such as.NET and Unity). In Visual Studio 2017, you can use File - Source Control - Advanced - Change Source Control to open the Change Source Control dialog: NOTE: The black bars are intentional. Now, all you have to do is select the unbound solution file and click the Bind item from the top menu of the dialog. Visual Studio Team Foundation Server 2015 is a source-code-control, project-management, and team-collaboration platform at the core of the Microsoft suite of Application Lifecycle Management (ALM) tools, which help teams be more agile, collaborate more effectively, and deliver quality software more consistently.
I couldn't for the life of me figure out why it wouldn't let me check the project in, as it had before.
Visual Studio Mac Tfs
Until I noticed something:
Normally, when you have a file checked in to TFS, a little icon appears next to that file. Said icon could be a blue padlock (not checked out to you), a green plus (pending add), a red check (checked out to you), or various other symbols. But my solution file (.SLN) did not have any icon at all.
This told me that it wasn't checked in to TFS, which I knew was highly improbable since I had pulled this particular project to my machine from our TFS server a few weeks ago.
Using Tfs With Visual Studio
The actual problem was that the solution file had somehow become unbound from our source control server. This means that TFS no longer tracks the file, and cannot record any changes made to it. I still do not know how the solution file became unbound, but frankly I don't care; I just needed to add my new project to the solution.
A little bit of research later, I figured out how to fix this problem. In Visual Studio 2017, you can use File -> Source Control -> Advanced -> Change Source Control to open the Change Source Control dialog:
NOTE: The black bars are intentional.
Now, all you have to do is select the unbound solution file and click the Bind item from the top menu of the dialog. If Visual Studio can find the bindings (which, in my case, it could) then your solution will be rebound to TFS and you can add your project as your normally would.
Happy Coding!
I recently had a problem in which I could not add a new project to an existing solution which was bound to TFS source control. The only option I would get when I right-clicked on the new project was Source Control -> Add Solution to Source Control, which looked something like this:
I couldn't for the life of me figure out why it wouldn't let me check the project in, as it had before.
Until I noticed something:
Normally, when you have a file checked in to TFS, a little icon appears next to that file. Said icon could be a blue padlock (not checked out to you), a green plus (pending add), a red check (checked out to you), or various other symbols. But my solution file (.SLN) did not have any icon at all.
This told me that it wasn't checked in to TFS, which I knew was highly improbable since I had pulled this particular project to my machine from our TFS server a few weeks ago.
The actual problem was that the solution file had somehow become unbound from our source control server. This means that TFS no longer tracks the file, and cannot record any changes made to it. I still do not know how the solution file became unbound, but frankly I don't care; I just needed to add my new project to the solution.
A little bit of research later, I figured out how to fix this problem. In Visual Studio 2017, you can use File -> Source Control -> Advanced -> Change Source Control to open the Change Source Control dialog:
NOTE: The black bars are intentional.
Now, all you have to do is select the unbound solution file and click the Bind item from the top menu of the dialog. If Visual Studio can find the bindings (which, in my case, it could) then your solution will be rebound to TFS and you can add your project as your normally would.
Happy Coding!