SourceSafe

How does it work for you?

[RossWal]

Is anyone using SourceSafe for their web development? Any comments on what's working for you would be most welcome.

Are you using it integrated with VisualStudio.net or FrontPage? Or as a standalone repository?

Do you use labels? At the project or file level?

What version of SourceSafe are you running?

[duckhunter]

I have used it for some time and I won't complain as it has done what we expected (just not much else) All it really offers is a code repository with history. We DO use labels and they help to keep track of what project is going when and what version of the file to rollback if needed.

Large multi-user, multi-project situations tend to create a little code confusion but we get around it.

Looking into PVCS as an alternative [merant.com ]

[RossWal]

Thanks Duckhunter.
We've used it for a long time on VB apps (desktop & dlls) and are just now considering it for our web sites. Do you label and republish entire sites for each update, or just the changed pages? Do you make a distinction between coded pages and generic content? Labeling everything for each update seems just too unweildy, but I'm not sure where to draw the line.

Thanks,
Ross

[duckhunter]

No distinctions between types of code and we only Label what is changing. That way we can get a complete list of changed files/dll/exe's for a production push.

[aspdaddy]

I used it last year, not by choice, I diddnt get on with it really, just adds hassle.

If I had to use it again I would wait until the site is at least on the test server before checking anything in, its just a pain having to keep checking files in and out to make edits.

Theres also nothing to stop a colleague editing a file without checking it out, and that can cause problems.

Another member here wrote an addin to update the comments on asp pages wwhen you check them in, that was its most useful feature I found.