Visual SourceSafe: Architecture/Management

Posted by Nic on Stack Overflow See other posts from Stack Overflow or by Nic
Published on 2010-04-13T20:27:13Z Indexed on 2010/04/13 20:53 UTC
Read the original article Hit count: 642

I was looking for information on how other people with larger teams manage SourceSafe currently. I was looking for recommendations and advice for a new project I was setting up that will allow for a few key things

  1. Scalability
  2. Manage multiple overlapping releases
  3. Geared more around .NET however allows for legacy applications (VB, ASP and VBS)

I am really looking for any lessons learned from other teams. I come from a StarTeam background and we used view labels and release labels to manage multiple overlapping projects. View labels geared more towards compiled code and SQL and the revision labels were used for VB/ASP projects.

Thank you for any advice and sharing your experience and frustrations with other companies you might have worked with in the past.

© Stack Overflow or respective owner

Related posts about visual-sourcesafe

Related posts about source