I copied my project in a new branch but it keeps referencing the sub-projects from the previous solution.
I chose "Set working folder" and selected the new folder on my local machine. I, also, selected the checkbox that applies the same changes to the subfolders. Everything looked fine until I tried to check out a file. As soon as I do the check out my subprojects reference the original solution again.
Then, I deleted my local reference to the project and went to Vault to open the project again. I selected "Open from Source Control" , selected a folder for the solution and opened it. Again all references looked fine. However, as soon as I tried to edit a file, the settings changed again.
I do not know what I am doing wrong.
Any suggestions?
Thank you very much.
Unable to access the correct projects
Moderator: SourceGear
This is a known issue with branching and Visual Studio. VS doesn't update its bindings to reflect the branch.
See http://support.sourcegear.com/viewtopic.php?t=1917 for how to address it.
See http://support.sourcegear.com/viewtopic.php?t=1917 for how to address it.
Thank you very much for your fast reply.
I followed the link and reached the article that explains how to fix the bug:
http://support.microsoft.com/default.as ... -us;317925
However, this article says that
"This bug was corrected in Visual Studio .NET 2003." and I am using VS 2003.
I still tried what they say in the article but it did not help. Do you know if the bug was actually fixed?
Thank you!
I followed the link and reached the article that explains how to fix the bug:
http://support.microsoft.com/default.as ... -us;317925
However, this article says that
"This bug was corrected in Visual Studio .NET 2003." and I am using VS 2003.
I still tried what they say in the article but it did not help. Do you know if the bug was actually fixed?
Thank you!
Thank you for your reply. However, this did not help as well.
Actually, I am not sure whether I explained the problem very well.
I do not try to just change the binding source for a solution. By creating the branch I created a completely new solution as a separate project.
I "set the working folder" and then I opened the project from VS with "Open from Source Control".
I noticed that actually not the binding of the new branch changes but the source binding of the original solution. When I check out a file the corresponding project of the original solution changes its binding to the new branch.
Any suggestions what the problem could be?
Thank you very much.
Actually, I am not sure whether I explained the problem very well.
I do not try to just change the binding source for a solution. By creating the branch I created a completely new solution as a separate project.
I "set the working folder" and then I opened the project from VS with "Open from Source Control".
I noticed that actually not the binding of the new branch changes but the source binding of the original solution. When I check out a file the corresponding project of the original solution changes its binding to the new branch.
Any suggestions what the problem could be?
Thank you very much.
Setting the working folder from the GUI client won't have any effect on Visual Studio if you do an Open From Source Control, because VS will set the working folder when it opens.
The problem either way though is that solution and project file contains bindings for the wrong folder in source control, and will need to be unbound to where it is incorrect, then rebound to where it should go. Doing so will cause changes to the solution/project file itself, so they will need to be checked in after they are modified locally.
The problem either way though is that solution and project file contains bindings for the wrong folder in source control, and will need to be unbound to where it is incorrect, then rebound to where it should go. Doing so will cause changes to the solution/project file itself, so they will need to be checked in after they are modified locally.