Scott Hanselman posted up a good piece on his blog about how they layout their source tree. He mentions quite a few good tools but gets down into specifics about how they lay things out. My builder managers toolkit pretty much includes these things:
- CVS or SVN today, Hatteras tomorrow.
- NAnt today, MSbuild tomorrow.
- FxCop today and tomorrow.
- Draco.NET today, Team System tomorrow.
- MbUnit today, built-in VS2005 tomorrow.
Now when it comes to laying out my filesystem - I do this and it just seems to work really nicely.
- ModuleDirectory\
- Module.build
- Module.FxCop
- Source\
- SolutionDirectory\
- ProjectDirectory\
- ProjectDirectory\
- ProjectDirectory\
- Documentation\
- Tools\
- NAnt\ (copy of NAnt)
- MbUnit\ (copy of MbUnit)
- Build\ (custom NAnt tasks)
- FxCop\ (copy of FxCop)
- Templates\
- AssemblyVersionInfo.cs
- Keys\
- Organisation.snk
Of course, this is just one module in CVS – it fits into a much larger picture.
Your site sure looks like an ass (not a good kind of ass) in firefox.
anyways, i’ve been looking at MSBuild but can’t find any fresh articles… all the feature overviews i’ve seen are from the time when it was first displayed.
The main thing I want to know if it can build SLN files without VS installed. Anyways, if you have any good links, would you mind posting them?
Thnx!
Hi Alex,
Thanks for the feedback. I’m waiting for a next generation blogging engine to come along and make my life better
MSBuild will be able to build sln files without Visual Studio installed - in fact the SLN file is just a MSBuild SLN file. One of the design goals for the MSBuild team was to make that work.
Dude, do you know of any good articles or SOMETHING that talks about msbuild?? I’m having no luck at all finding any descent info on it
Hi Alex,
The MSBuild Wiki is up and is pretty good. If I can find the time I hope to post up some entries about MSBuild.