Thursday, July 20, 2006

Visual Studio 2005 and Visual Source Safe

After spending quite a bit of time playing with Menus on my Visual Studio 2005 to find the option of "Add my solution to Source control " that was there in my prev VS version I realized that I had not installed Source control at all . This was weird as I did not remember explicitly unchecking any of the options except VJ# which i thought I was not going to need probably.

I ran setup again chose Add Remove and could not find the installtion Option.
Anyway after a few painful hours I have finally got it to work . This is what I had to do

1. ) Get the VS 2005 CD . Browse to the VSS folder and run Setup .
2. ) You need the first check box in the custom installtion . Everything else is really optional
3.) Install the Visual Source safe client and connect to your existing Sourcesafe Manully
4.) Fire up Studio, and go to Tools > Options > Source Control> Show all settings > Select the current source control plug-in to "Microsoft Visual SourceSafe"

Well I hope that helps some of you atleast ! If it did leave me a note !

23 comments:

O said...

Thanks, it helped me!

Anonymous said...

Yo saved my day!
Thanks a lot!

PD: damm obfuscated MS people :-/

Shreedhar said...

Thanks a lot. Really this helps me a lot.

Anonymous said...

Thanks! You saved me a lot of time in finding that obscurely hidden setting.
I just love the way studio told me I need to install a plugin that is already installed, but just not selected.

ullmannn said...

Thanks, this helped me a lot. No other post or MS Help mentioned to go into Tools > Options.

Anonymous said...

I have followed the directions and everything is great up until step 4. I do not get Source Safe under Tools/Options. I am able to see this on other developers PCs but not mine. I cannot figure out whtat step am I leaving out?

Anonymous said...

Thanks for that - just what I needed after several hours of frustration.

Anonymous said...

Thanks for posting this. I did not know how to hookup Visual Studio 2005 with Visual Source Safe. I spent hours trying to figure out how the software connect and talk to each other. Your fourth instruction was the key. 4.) Fire up Studio, and go to Tools > Options > Source Control> Show all settings > Select the current source control plug-in to "Microsoft Visual SourceSafe". Again Thanks alot.

Anonymous said...

Ditto the previous poster. THANK YOU FOR POSTING THIS!!!!

Anonymous said...

thanx dear
Asad jahangir khanzada

Anonymous said...

Thanks a lot.. That was not so obvious and not mentioned in any MS sites

lippike said...

You saved the day :)
Zhanks for this post.

butchi said...

Really helpful, thx! :)

Anonymous said...

...you saved me a lot of time - thanks!

oliver

Anonymous said...

Yep, same Here !

Dudemeister said...

I love you :)

Anonymous said...

Thank you a bunch. this is very helpful. I can't believe that it doesn't exist on msdn for VS 2005

Govind PreetSingh said...

Hi, I agree, a very handy 4 step process. but may I remind everyone, that we as developers are also expected to think out of the box.. I read in one of the comments above, that he cannot see "Source Control" in Options.. dude, you are not missing on any step.. think out of the box.. if you do not see that option, still check the "Show All Settings" checkbox.. it will show you something if not the same.. understand the character of the technology, and not just the what you see thing..! Best of Luck everyone.
PS: I say the above, because it happened the same with me.. my Visual Studio 2005 also did not show me that option, I just went ahead and checked the "Show All Settings" checkbox, and it showed the Source Control Option there.. hope it helps!
Govind

Anonymous said...

[QUOTE]Hi, I agree, a very handy 4 step process. but may I remind everyone, that we as developers are also expected to think out of the box.. I read in one of the comments above, that he can[/QUOTE]

This is such a dumb thing to say I had to comment. "Think outside the box," should not be conflated with "Abide by someone elses shitty design, show no frustration, just go with whatever the geniuses at microsoft decide to throw at us."

The placement of this option is NOT INTUITIVE. Rather than us "thinking outside the box," they should LEARN TO DEVELOP USABLE SOFTWARE; and if you can learn to do the same; YOU will be thinking outside the box.

Anonymous said...

Govind,

Never mind, just realized that you're another brainless indian programmer who fucks up every damn piece of code he writes

NrusinghaNathAcharya said...

Thanks man.
Great steps, Saved One more day

Anonymous said...

Thank you. It really help me)))

Anonymous said...

4 years later, your post is still helpful :)