VS2008 source control integration
-
Is anyone else in a position of using two source control providers in VS2008 ? It flat out does not work. I am opening my project and it insists I am using providerA, when I am using providerB for this project. Trying to change it, the project just closes. Going to the change source control tab also flat out does not work. It's a disaster.
Christian Graus Driven to the arms of OSX by Vista.
-
Is anyone else in a position of using two source control providers in VS2008 ? It flat out does not work. I am opening my project and it insists I am using providerA, when I am using providerB for this project. Trying to change it, the project just closes. Going to the change source control tab also flat out does not work. It's a disaster.
Christian Graus Driven to the arms of OSX by Vista.
I refuse to let any source control system integrate with Visual Studio. I'll go so far as to delete or rename extension DLLs to keep it from happening. I love having source control available, but when i'm in VS i'm coding and i don't want to be interrupted by dialogs asking me to check out files or long delays while the solution tree state is synchronized. Every so often, i'll upgrade a provider and put up with integration for a few days before disabling it again - and every time, i get fed up with the brain damage and disable it. So, no, i don't have any of the problems you describe. :-\
----
You're right. These facts that you've laid out totally contradict the wild ramblings that I pulled off the back of cornflakes packets.
-
I refuse to let any source control system integrate with Visual Studio. I'll go so far as to delete or rename extension DLLs to keep it from happening. I love having source control available, but when i'm in VS i'm coding and i don't want to be interrupted by dialogs asking me to check out files or long delays while the solution tree state is synchronized. Every so often, i'll upgrade a provider and put up with integration for a few days before disabling it again - and every time, i get fed up with the brain damage and disable it. So, no, i don't have any of the problems you describe. :-\
----
You're right. These facts that you've laid out totally contradict the wild ramblings that I pulled off the back of cornflakes packets.
I agree with Shog. I've gotten so used to using SVN (with Tortoise SVN) outside of Visual Studio, that I don't even think about it any longer. :)
WE ARE DYSLEXIC OF BORG. Refutance is systile. Your a$$ will be laminated. There are 10 kinds of people in the world: People who know binary and people who don't.
-
I agree with Shog. I've gotten so used to using SVN (with Tortoise SVN) outside of Visual Studio, that I don't even think about it any longer. :)
WE ARE DYSLEXIC OF BORG. Refutance is systile. Your a$$ will be laminated. There are 10 kinds of people in the world: People who know binary and people who don't.
I've been using this... Works fine... http://ankhsvn.open.collab.net/[^]
Free your mind...
-
Is anyone else in a position of using two source control providers in VS2008 ? It flat out does not work. I am opening my project and it insists I am using providerA, when I am using providerB for this project. Trying to change it, the project just closes. Going to the change source control tab also flat out does not work. It's a disaster.
Christian Graus Driven to the arms of OSX by Vista.
We've moved to SVN and VisualSVN. It's awesome. Integration with VS 2008 is seamless. And I've never been able to say that about source code integration before. Ever.
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Is anyone else in a position of using two source control providers in VS2008 ? It flat out does not work. I am opening my project and it insists I am using providerA, when I am using providerB for this project. Trying to change it, the project just closes. Going to the change source control tab also flat out does not work. It's a disaster.
Christian Graus Driven to the arms of OSX by Vista.
I believe you need to change the source control provider before opening the project (and preferably after a VS restart).
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
My latest book : C++/CLI in Action / Amazon.com link -
Is anyone else in a position of using two source control providers in VS2008 ? It flat out does not work. I am opening my project and it insists I am using providerA, when I am using providerB for this project. Trying to change it, the project just closes. Going to the change source control tab also flat out does not work. It's a disaster.
Christian Graus Driven to the arms of OSX by Vista.
Christian Graus wrote:
in a position of using two source control providers in VS2008
Nope, and thankfully so :) Pretty much have stuck with svn...
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
We've moved to SVN and VisualSVN. It's awesome. Integration with VS 2008 is seamless. And I've never been able to say that about source code integration before. Ever.
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
We've moved to SVN and VisualSVN. It's awesome. Integration with VS 2008 is seamless. And I've never been able to say that about source code integration before. Ever.
cheers, Chris Maunder
CodeProject.com : C++ MVP
I second the Visual SVN recommendation - for normal day-to-day source control. Though we are only just starting to set up our branch/merge strategy (everything is on trunk at the mo) so I'll reserve judgement until I see how easy that is. I must say it's more than a trifle annoying that there seems no indicator in VS as to which branch you are connected - and most tortoise boxes ony show the local path. The Java guys using Subclipse can see what branch they are in. Still, I am sure we will work it out. I kinda miss the VSS 'locked' icon though so you know someone else is working on stuff. Still, locking source is a whole different strategy... (Which you can do in SVN, it's just you get no indication - until you try to commit. Not quite the same)
-
I second the Visual SVN recommendation - for normal day-to-day source control. Though we are only just starting to set up our branch/merge strategy (everything is on trunk at the mo) so I'll reserve judgement until I see how easy that is. I must say it's more than a trifle annoying that there seems no indicator in VS as to which branch you are connected - and most tortoise boxes ony show the local path. The Java guys using Subclipse can see what branch they are in. Still, I am sure we will work it out. I kinda miss the VSS 'locked' icon though so you know someone else is working on stuff. Still, locking source is a whole different strategy... (Which you can do in SVN, it's just you get no indication - until you try to commit. Not quite the same)
We've had many a discussion on whether to move to a 'Lock and Edit' mode or stay with the default. We've had a few cases of conflicts but nothing (for a while) that's caused serious angst. At least we're no longer having the "Argh! The file is locked!" Friday night screams of anguish.
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Is anyone else in a position of using two source control providers in VS2008 ? It flat out does not work. I am opening my project and it insists I am using providerA, when I am using providerB for this project. Trying to change it, the project just closes. Going to the change source control tab also flat out does not work. It's a disaster.
Christian Graus Driven to the arms of OSX by Vista.
It's controlled by a registry entry as a global setting, not at the project levl. :wtf: I use this to switch to the proper one prior to starting VS up and opening the project. http://www.codeproject.com/KB/applications/sccswitcher.aspx[^]
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall