Guidelines on structuring code for .net projects

Question

I generally use IoC pattern in my projects which are most of the time ASP.net based. Are there any guidelines on how to structure the projects in a general 3 layered project UI+BL+Data Access. I want to know more about how the folders should be created, where should constants be kept at within each layer (I keep all the strings such as query string parameters, stored procedure parameter etc in file named Constants which is singleton). How should I create classes that interact with Data Access layer from Business Layer etc. and all such code structure questions.

Is there any guidance or a book on this?

Answer 1

Microsoft has a plethora of information on this. I've used Microsoft .NET: Architecting Applications for the Enterprise as my bible for software architecture

http://www.amazon.com/Microsoft%C2%AE-NET-Architecting-Applications-Pro-Developer/dp/073562609X

Check out this MSDN guide as well

http://msdn.microsoft.com/en-us/library/ff647095.aspx

Also, take a look at some application frameworks like Sharp Architecture for examples

http://sharparchitecture.net/

A lot of NHibernate tutorials demonstrate software design principles that can be applied to any solution

http://nhforge.org/blogs/nhibernate/archive/2010/04/25/first-three-nhibernate-quickstart-tutorials-available.aspx