How to deploy SourceSafe?

Wanting to set it up for a multi developer environment

[RossWal]

Has anyone out there designed a SourceSafe environment for a multi developer project. Though I hate to use the term, I guess I'm lookoing for "best Practices". I googled around, but didn't come up with much.

I'm interested in how many libraries to create, checkout check-in procedures, merits of integrating with visual studio, etc.

Thanks for any tips.

Ross

[Easy_Coder]

Take a look here: [msdn.microsoft.com...]

I think you'll find that once your done getting it set up that it's not that difficult.

[KillerG]

A coworker and I use VSS with Dreamweaver. It's not foolproof but it gets the job done. Just make you always have the latest version pulled down before doing and work and communicate with the others on what you will be working on.

[trillianjedi]

I use it with Visual Studio with which it bolts straight in (designed to be used with it) and that's a merit if you use VS.

It's ok - it works, but it's a little tricky to use at first.

I much prefer CVS now (free, open-source and x-platform too). I find that easier to setup and more intuitive to use.

TJ

[RossWal]

I've used SS for years, but mostly for desktop applications written in VB. That seems to be a more structured environment that web sites that in this case have ASP code, ASPX executables & other resources, com dlls, and lots and lots of plain old content.

What I'm struggling with is the best way to structure libraries. Should I have one for ongoing activity, and a redundant one for code deployed on the Production site?

Should we lockdown and keep versioned backups for plain content?

It's a mess. I'm surpised MS doesn't provide suggestions on how to deploy the SS tool. Not the mechanics of how to use it, but the strategy for setting it up.

Thanks for your thoughts.

Ross

[TheNige]

Try Team Development with Visual Studio® .NET and Visual SourceSafe™ [msdn.microsoft.com]