Visual Studio source control hell
-
What about trying to manually edit the solution file? Perhaps remove references to source control.
I've tried to search the whole project for references to the provider and not found them. I guess I will look at the XML next.
Christian Graus Driven to the arms of OSX by Vista.
-
It's that goddamn Mac. You should have expected a certain level of incompatibility. :)
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001ROTFL. Yeah, right.
Christian Graus Driven to the arms of OSX by Vista.
-
What about trying to manually edit the solution file? Perhaps remove references to source control.
This usually works for me.
"Make everything as simple as possible, but not simpler." - Albert Einstein
Jason Henderson
-
ROTFL. Yeah, right.
Christian Graus Driven to the arms of OSX by Vista.
She's hot, she's easy, but she sure as hell doesn't want you to know what she did in the past.
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
-
This usually works for me.
"Make everything as simple as possible, but not simpler." - Albert Einstein
Jason Henderson
It *was* working for me, and I did a get latest, and now the source is not bound, but I still can't change my source provider without it telling me it will close the project. b/c I am on a Mac anyhow, I am seriously considering having one XP VM for DIA and one for Intravet.
Christian Graus Driven to the arms of OSX by Vista.
-
She's hot, she's easy, but she sure as hell doesn't want you to know what she did in the past.
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
wow thats my gf!! :)
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
-
wow thats my gf!! :)
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
Ooooh, uhm, oh damn, it's the Lounge! :)
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
-
So, it's been several days and still, EVERY time I open my project, it tells me it can't find the source control, and the reason is that it insists on using the wrong source control provider. EVERY time I open my project, I have to remove source control and rebind to the right provider. Does anyone have any experience with this ?
Christian Graus Driven to the arms of OSX by Vista.
This is one reason why a lot of people don't bother and use external applications for this..
John
-
So, it's been several days and still, EVERY time I open my project, it tells me it can't find the source control, and the reason is that it insists on using the wrong source control provider. EVERY time I open my project, I have to remove source control and rebind to the right provider. Does anyone have any experience with this ?
Christian Graus Driven to the arms of OSX by Vista.
Visual Studio has a couple ways of binding the project to source control. In the one method, they put the source control information in the project file. In the other, the project file is marked to look in the solution file instead. I have a feeling your project file is marked with source control information. I would delete your solution file, and then edit the project file manually. If you open it in Notepad, you'll see four attributes whose names begin with "Scc". Change the values of all of those to "SAK", which appears to be a marker that means 'look in the solution file'. Open the project in Visual Studio and do a 'save all' to save a new solution file. You should then be able to use 'change source control' to add the solution file back to source control.
Software Zen:
delete this;
Fold With Us![^] -
Visual Studio has a couple ways of binding the project to source control. In the one method, they put the source control information in the project file. In the other, the project file is marked to look in the solution file instead. I have a feeling your project file is marked with source control information. I would delete your solution file, and then edit the project file manually. If you open it in Notepad, you'll see four attributes whose names begin with "Scc". Change the values of all of those to "SAK", which appears to be a marker that means 'look in the solution file'. Open the project in Visual Studio and do a 'save all' to save a new solution file. You should then be able to use 'change source control' to add the solution file back to source control.
Software Zen:
delete this;
Fold With Us![^]Thanks, I will give that a try.
Christian Graus Driven to the arms of OSX by Vista.
-
So, it's been several days and still, EVERY time I open my project, it tells me it can't find the source control, and the reason is that it insists on using the wrong source control provider. EVERY time I open my project, I have to remove source control and rebind to the right provider. Does anyone have any experience with this ?
Christian Graus Driven to the arms of OSX by Vista.
Subversion[^] + Tortoise[^]= Win
// Steve McLenithan
-
So, it's been several days and still, EVERY time I open my project, it tells me it can't find the source control, and the reason is that it insists on using the wrong source control provider. EVERY time I open my project, I have to remove source control and rebind to the right provider. Does anyone have any experience with this ?
Christian Graus Driven to the arms of OSX by Vista.
Have you considered decoupling the source control provider from the IDE? You seem to get into an awful lot of problems with technology.... :suss:
Cheers, Vıkram.
Stand up to be seen. Speak up to be heard. Shut up to be appreciated.
