Folowing the first post on this topic, and regarding the folder structure, I'm using the How To: Structure Your Source Control Folders in Team Foundation Server guidance, with some "minor" changes.

Dependencies

All extenal references needed by this project will land here. In this case, assemblies like log4net.dll, RssToolkit.dll will live here.

Maintenance

The maintenance folder keeps all the old versions in case we need to change something on a production enviroment that has a old version.

Release

The lastest version of our application is kept here, for easy deployment. It also has the documentation, unit tests and code coverage reports.

Scripts

The nant scripts reside in here.

Source

Well, this seems obvious.

Tools

This folder shouldn't bellong to the application, but rather to the development enviroment. In where we will keep tools needed for the development of our applications. This should be keept updated with the latest versions.

You may be asking: "Why do you also keep the log4net and the AspnetRssToolkit also on this folder? why not reference to where instead?"

I choosed to copy the references to the project because I could be developing with a different version. In this particular project this will probably not happen, but when working on multiple solutions in a team enviroment, it is best, in my opinion, to keep the project references in a solution folder. This way you know (or at least expect :) )that the project will build with that set of assemblies.

Any opinions on this structure?