My team and I are working with a VisualStudio solution under the VSS source control. We have several projects under our one solution.
We are planning on moving to Git and we would like to have a migration phase where we would have X projets under VSS source control and Y projects under Git source control.
The main problem here is that when I try in Visual studio (2010 or 2012) to go to "File" => "Source control" => "Change source control", I can't unbind only one project, they are all selected and I can only unbind them all.
Is there a way to unbind one of the Visual Studio projects and keep the others bound to VSS ?
Thanks for your help.
Florian.
I think you can create two solution files for the projects using VSS and Git.
Try the steps like below:
Unbind the whole solution from VSS
Create a copy of the solution and you can copy the projects for Git from here.
Bind back the solution to VSS source control in Visual Studio
Remove the projects for Git from the VSS solution
Related
Last Friday I started a project in Visual Studio 2012. We use Visual SourceSafe 2005 for our source control. I wish I hadn't done this, but I did, when I created the project in VSS 2005, I put it at the root level. I didn't realize my mistake until today. We have a root level project that would have been much more appropriate to have put this into, but I didn't do that.
So here are my questions. First, is it possible to move a project in VSS 2005's Visual SourceSafe Explorer, from one place (the root level) to another place (under a different root level folder)? Where it is on any of our development machines is a different issue, I just want to move this project, within VSS, to where it should be, where other developers will look for find it.
Second, if it is possible to do this, then how do I do it?
You can try the steps below:
In Visual SourceSafe Explorer, you can use the menu File->Move command to move your project.
In Visual Studio, please go to File->Source Control->Change Source Control and update the mapping to make sure it uses the new server path.
I have Visual Studio 2012 solution with multiple BI projects. One of the SSIS projects do not show all the ssis packages in the Solution Explorer (checked in by another teammember). But the missing files are in the TFS (Source Control Explorer) and are visible in the physical folder.
I tried "Show all files" did not work.
I tried adding the file again but the project does not allow that saying "file with same name exists".
Any idea what is going on here
The authoritative source of what's in a project is going to be the ProjectName.dtproj file.
Inside of that will be entries for the packages that comprise the project. For a non-package deployment model, it's trivial to edit the file by hand and make your stuff show up.
It's way too much effort to do that by hand for a 2012+ project deployment model. Open the Project in Visual Studio (ssdt/bids) and right click on the project. Click Add Existing Item (not add package) and then click the "missing" package. Check your .dtproj file in and all is right with the world.
I had the same issue in 2020, I managed to solve it by building the solution.
On the menu select Build-> Build Solution OR Ctrl+Shift+B
I inherited a project at my new company that used to connect to a TFS server. Now I only have the zip of the source/solution which I have dumped into my Kiln (mercurial) repo.
The issue I am having is every time I open the solution I see this prompt
"Please provide credentials to connect to team foundation server"
If I hit cancel I see this...
Any ideas as to how to avoid this every time I open the solution?
You need to remove the binding to TFS from the inside your projects.
In Visual studio, with the projects loaded, open the file menu->source control->change source control->Unbind for all the projects.
This will remove a section of xml from your .csproj (or whatever type).
Save your projects and you should be free of TFS.
This is very weird behavior of Visual studio and TFS. I am using Visual Studio 2012 and TFS 2012. We have a large number of projects and solutions in the source control.
Lets assume I have no pending changes.
Whenever I open solutions which are present on source control all projects are loaded. And not a single project is checked-out for edit. I can see lock icon with the projects in the solution explorer.
Now I create a new solution and add projects from the source control to this solution, I face weird behavior. Some of the projects are automatically checked out and I haven't did any change to it. And this happens to only few projects instead of all projects. If I call undo all pending changes TFS perform a undo but then calls checkout for the project.
What is the proper solution to it. And it happens only in custom solution (sln) which is not present in the source control.
When trying to switch my solution from using Ankhsvn to VisualHG (we've just migrated from SVN to Mercurial) I kept getting the following message:
"The active solution or project is controlled by a different source
control plug-in than the one you have selected. If you change the
source control plugin, the active solution or project will be closed.
Do you wish to continue?"
The solution would then close and when I re-opened it it would still be linked to Ankhsvn.
I tried deleting the source folder and grabbing a fresh clone out of Mercurial, but the problem kept coming back.
The solution required opening the .sln file in a text editor and manually removing the following block:
- GlobalSection(SubversionScc) = preSolution
- Svn-Managed = True
- Manager = AnkhSVN - Subversion Support for Visual Studio
- EndGlobalSection
After that I was good to go.
The above solution works but another way to do it without editing the sln is to open the project instead of the solution. Then change the setting at Tools->Options->Source Control->Plug-in Selection and change plug-in.
Make sure you save all - this should save the new Source control to the solution.
My solution is:
open solution normally with vs
disconnect all AnkhSvn project bindings
change source control plugin to VisualHG and save all