Our shop is new to VB2005 (formerly Delphi) and the team of 5 developers has
enough of a learning curve with VB and VS2005 that we are not yet
considering either VS-Team System or even Visual SourceSafe.  Does anyone
know of any good resources or general guidelines for solution/project
development using shared network drives as the source code repository?

Thanks

Dan W.

RTFM

Source safe is documented, read the documentation. THEN come back here with
any specific questions you may have. You are a "professional" developer,
then behave like one and use the provided resources.

A millisecond of thought would show that the repository MUST be on a network
share unless every developer takes it in turns to use the same single PC.
Also having the repository on a share makes backing up a doddle, you do back
your source up regularly don't you?

Dave O.

Show quoteHide quote

No coffee this morning? Someone stole your favorite donut? What the heck's
with the attitude? His only mistake was asking dotNet questions in a
non-dotnet group.

Can't stand coffee!
This forum is (I thought) for specific questions, not for "tell me
everything I might need to know about xxxx because I can't be bothered to
find out for myself"
Also from the way he posed the question he is a professional developer, in
which case he should act with some professionalism and find out what he can
first.
We are here to help and point in the right direction, not hand-holding. If
he comes back with a specific question I will be only too happy to help.
Sometimes you need to be cruel to be kind.

Regards
Dave O.

Show quoteHide quote

It's not a .NET question at all; it's a SourceSafe question. And it is
pretty much an RTFM thing. I knew nothing about SourceSafe when I first
started and I figured it out pretty quickly just from the docs.

Curb the Attitude Dave0 and Read The Fn MESSAGE...We're not using VSS.  Just
looking for some informed pointers on sharing source code via a network
drive.

My mistake on the incorrect newsgroup.  I'll post to the vsnet.general.


Show quoteHide quote

Oh, yes, I see that now. So here's your answer about best practices for
sharing source code on a network drive: DON'T DO IT. Use a source code
control provider or you're just setting yourself up for pain.

And the best information you will find is in the SourceSafe documentation -
Read it!

If you have some philosophical reason for eschewing SourceSafe then you must
have already done the research, if it is just a "Microsoft Bad - Anything
else Good" well in some cases that may be valid, but not in this one and
never without doing the basic research. And research does not mean just
asking here.

The paucity of competing source code control applications may suggest that
SourceSafe does the job needed of most developers.

If you were just asking about how to stick the source on a share with no
administration application, forget it, you WILL screw up and unlike
SourceSafe you will have no comprehensive facility to roll back to any
previous source.

I don't have a bad attitude, just trying to point you in the right
direction, if you want to do it a different way don't come crying to us when
you lose some source code.



Regards

Dave O.


Show quoteHide quote

released on Wed, 28 Feb 2007 09:36:12 -0600 bearing the
following fruit:

Source safe is easy to use - seriously!

You don't have to use the more advanced functionality.

Also, just in case your not aware, this is a VB6 group so we
won't be able to help you with the use of source safe and
VB2005.

Within a *.exe
Function that returns an Array
Reason for 'Set' keyword
SendKeys command fails on Vista
Error in reading large csv file
Sending email
Should I or shouldn't I include excel.exe in my app distribution package?
Getting Info from a .TTF File
Run-time Error 430, WITH non-broken binary compatibility?
TaskBar won't show when hidden.