Mike Roberts posted a deep and interesting article on development.
From his blog:
In my career I've setup quite a few development trees for .NET projects. What do I mean by a 'development tree'?
- It is a directory structure
- containing:
- source files
- tools and dependencies
- references to external tools and dependencies
- checked into source control
- that is atomically integratable
- to produce a set of artifacts
A good development tree should:
- be easily integratable on new environments
- require little maintainance
- but be easily maintainable when it does require maintenance
- support, but not hamper, developer productivity
- have consistent behaviour
These are rather qualitative ideals, but give some direction about where we want to head.
In this article I show how to develop a good 'boilerplate' development tree structure for .NET projects that other people can use.