Help Needed: Source Safe and VS.NET

  • Thread starter Thread starter Mihen
  • Start date Start date
M

Mihen

Hi,

I and my friends have just started using Visual Studio .NET 2003 for
our software development.
We are using Visual Source Safe to manage the source control.
However, we found that we're not so that good to utilize the Source
Safe.
We faced the following issues in our daily life:

1. Most of us always forget to check in our work to Source Safe and
we're also not used to do get latest version of all files from source
safe and as a result, everyone doesn't get the latest version. Is
there any way to automatically get the latest version of files
from Source Safe when we start Visual Studio.NET? And also how to
remind people not to forget to check in their work?

2. Is it better to allow multiple checkout option? I've heard that
it's better not, but I found that the solution file (*.sln) has to be
multiple check out otherwise it's really difficult to modify the
project & all the files.


I appreciated much any suggestions

Many Thanks in advance

Hendry
 
Check out the Tools menu, Options then Source Control.

You can force VS to check in when you close the solution.

We don't use multiple checkouts - at least then there are no complications -
you've got the file or you haven't. We only check out .sln or .vbp files
when we need to, and check them in as soon as we've finished. It works
really well - hats off to Microsoft as we'd all be in a terrible muddle
without sourcesafe!

Mihen said:
Hi,

I and my friends have just started using Visual Studio .NET 2003 for
our software development.
We are using Visual Source Safe to manage the source control.
However, we found that we're not so that good to utilize the Source
Safe.
We faced the following issues in our daily life:

1. Most of us always forget to check in our work to Source Safe and
we're also not used to do get latest version of all files from source
safe and as a result, everyone doesn't get the latest version. Is
there any way to automatically get the latest version of files
from Source Safe when we start Visual Studio.NET? And also how to
remind people not to forget to check in their work?

2. Is it better to allow multiple checkout option? I've heard that
it's better not, but I found that the solution file (*.sln) has to be
multiple check out otherwise it's really difficult to modify the
project & all the files.


I appreciated much any suggestions

Many Thanks in advance

Hendry
Click to expand...
 
Sparky said:
Check out the Tools menu, Options then Source Control.

You can force VS to check in when you close the solution.

We don't use multiple checkouts - at least then there are no complications -
you've got the file or you haven't. We only check out .sln or .vbp files
when we need to, and check them in as soon as we've finished. It works
really well - hats off to Microsoft as we'd all be in a terrible muddle
without sourcesafe!
Click to expand...

Well, there are plenty of other source control products out there.
Personally I've had *tons* of trouble with source safe - it's corrupted
files loads of times, it's a pig to work with over a VPN, the user
interface has a load of nastiness, etc.

I've heard that when Whideby launches, MS will also be launching a new
source control system. I certainly hope that's true, and that it will
have a smooth upgrade path from VSS. It's only the potential for losing
histories etc during transitions that's stopped me from strenuously
recommending that we move to Subversion or something similar.
 
Back
Top