I've been looking all over for some good, real-world example subversion structures for ASP.NET websites and have only come across a few. I haven't really used any source control other than storing my code in a repository so it's not just on one computer.
I've found a blog that has a lot of good examples (http://ariejan.net/2006/11/24/svn-how-to-structure-your-repository/) but there's nothing for specific examples for an ASP.NET. There's some good ideas I found here (http://discuss.joelonsoftware.com/default.asp?dotnet.12.406052.3) but nothing about the best way to do it.
I like the idea of the standard branches/tags/trunk, but does that always work on large scale web applications? I started populating the trunk with the following folders:
- Database - contains a Red-Gate SQL Compare Snapshot of the database
- LLBLGen - contains the LLBLGenPro v. 2 project
- Libs - all .dll files that do not have source code associated with them, such as telerik controls, infragistics controls, browserhawk files, etc...
- Source - root for any class libraries, projects get their own folder on a per project basis
- Webroot - the root of the web application project
I want to put all releases in the tags directory, then any working changes into the branch directory based on the build number (which contains the date).
I think this is a good way to keep track of everything, but I'm very open to other suggestions.
12-15-2006 12:27 AM