Last post May 12, 2010 09:18 PM by rroman81
Dec 10, 2009 10:38 AM|MSUTech|LINK
We have not done much version control in the past.. but, we are getting to the point that we may have as many as 3 programmers working on a single .net/sql web-based application .... can someone give me the 'big picture' best practices way of keeping track
of what is what.. as well as what previous version was 'successfully' released.... also, can someone give me the more specific answer to what is the best application to use for this (sourcesafe? if so.. I have never used it)... we work primarily in a .net/visual
studio/sql server environment..
Dec 15, 2009 02:56 AM|Thomas Sun – MSFT|LINK
Since it is team project, I suggest you use Visual SourceSafe which is used for general team project. For more information about Visual SourceSafe, see
In your case, you can use 3-tiers architecture (Presentation, Logical, Data) for your ASP.NET website. By doing so, one developer can take responsibility for one tier. For more information, see
I look forward to receiving your test results.
Dec 17, 2009 02:23 PM|yonision|LINK
I'd strongly recommend you to stay away from SourceSafe. I work here for a company that manufactures a product that provides version control for SQL Server - something the market surprisingly neglected (http://www.nobhillsoft.com)
and I can tell you that SourceSafe has seen mass exodus in the past 2-3 years. Some people move to Subversion, which is stable, reliable and free (3 things that SourceSafe isn’t) and others move to MS Team Foundation Server, which seems like an overkill for
what you need right now (plus its REALLY expensive)
Microsoft themselves signal that they intend to remove SourceSafe from the market. They haven’t worked on it since 1996 (well in 2005 they added the word ‘Visual’ before it, but that’s about it) So I am surprised to see a Microsoft guy recommending it here.
Sorry, Microsoft – I do praise you when you do things right, and many times you do. But SourceSafe isn’t one of those cases.
For your needs go with Subversion, and you can google and find tons of articles on best practices etc.
Check out our product too;)
May 12, 2010 09:18 PM|rroman81|LINK
Stay away from VSS at all costs. It's dead and unsupported. More importantly, it's very hard to work concurrently.
I would suggest to move the SVN route, VisualSVN server, and read the SVN book. It's free and has guidance on how to get started.
For .Net integration, use AnkhSVN and tortoiseSVN on your workstations. If you want to get a supported client, use VisualSVN.
If you have access to MSDN, maybe you want to research how to get VS2010 TFS in-house.