How to write a good basic architecture for a project in ASP.NET MVC

Question

I need to write a large system in January with ASP.NET MVC3 / C #, and you need to know how to write a system that will WORK . I have some experience with ASP.NET MVC and C #, but I would not call myself an expert. It must be extensible so that I can extend it later with new features. How can I do that? Are there any books that explain this topic in detail or should I use a trial version and an error?

In short, I need to know good design practice in my code, which is expanding for the future.

Relations RaVen

The system will be a portal community with forum ratings, etc. I can’t say more than <Company policy →, I can manage the forums because of the many open source options ... But everything else depends on me.

Answer 1

Professional ASP.NET MVC 2 is a good starting point, although I would suggest that they come out with MVC 3 as well. The NerdDinner tutorial contains many ideas on how to structure your application.

: MVC, . , , , . , .

, . , , , . , , .

Answer 2

SOLID ==

SOLID , .

Answer 3

/ , SharpArchitecture - . ... , , , . , . NHibernate, Castle MVC.

Answer 4

Test Driven . , . MVC , .

Answer 5

""

http://awesome.codeplex.com

Answer 6

, , . , - , .

"" - . , , , .

Answer 7

, CMS , ASP.NET MVC, . , , . , , , .. , . , .

edit: , , .

Answer 8

WhoCanHelpMe . S # arp, MVC-, , . IoC db .

, , , jFar, SOLID .

MEF .