Hi,
I want some expert's advice.
Two ways we can use source safe.
1. Use Souce Safe explorer and Check In / Check Out from there
2. Add Project to source safe and do Check In/ Check Out from from Visual
Studio solution explorer.

I want to know which one is better to use or most commonly used and why.

Thanks,
Mike

Re: VB2005 Project with Source Safe by Andrej

Andrej
Sat Oct 15 18:17:01 CDT 2005

If you're working with source code, then the second way is a way to go.
Since you commonly check out only files you want to change, it's faster to
right click and check out the files from your VS IDE explorer than switching
to Source Safe. You only check out files you need and when you need them. VS
IDE also gives you a nice visual representation of the checked in/out
status. And when you have more than a few projects in your VSS database,
grouped in different solutions, browsing the VSS for a specific file you
want to check out is a pain.
VSS-VS integration is a convinient timesaver, basically.

Andrej

"Knoebel, Mike" <KnoebelMike@nospam.com> wrote in message
news:%23AkWqjP0FHA.2884@TK2MSFTNGP09.phx.gbl...
> Hi,
> I want some expert's advice.
> Two ways we can use source safe.
> 1. Use Souce Safe explorer and Check In / Check Out from there
> 2. Add Project to source safe and do Check In/ Check Out from from Visual
> Studio solution explorer.
>
> I want to know which one is better to use or most commonly used and why.
>
> Thanks,
> Mike
>



Re: VB2005 Project with Source Safe by Jon

Jon
Sun Oct 16 02:31:35 CDT 2005

<"Andrej Tozon" <andrej [at] tozon.info>> wrote:
> If you're working with source code, then the second way is a way to go.
> Since you commonly check out only files you want to change, it's faster to
> right click and check out the files from your VS IDE explorer than switching
> to Source Safe. You only check out files you need and when you need them. VS
> IDE also gives you a nice visual representation of the checked in/out
> status. And when you have more than a few projects in your VSS database,
> grouped in different solutions, browsing the VSS for a specific file you
> want to check out is a pain.
> VSS-VS integration is a convinient timesaver, basically.

It is when it works. It's a huge pain in the neck when it doesn't
(which is quite frequently, in my experience - especially when creating
new projects, or changing VSS databases).

Ironically, the VSS plug-in for Eclipse is much simpler in terms of
knowing what it's going to do at any point in time...

--
Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too