Question

I’m new to the MVC framework and have just run through the NerdDinner sample project. I’m loving this approach over form-based asp.net.

I’d like to spin of a more sizable side project using this same approach. Do you see anything in that project that would prevent me from enlarging the basic structure to a more complex website?

Examples of things that make me wary:
1) The NerdDinner sample accesses a db of only two tables, my db has around 30.
2) The NerdDinner project uses the LinqToSQL classes directly… all the way from the model, through the controller, to the view… is that kosher for a larger project?

Do you see any other parts of the NerdDinner framework that might cause me future grief?

Answer 1

I would add a service layer between the repositories and controllers. The service layer will contain all of your business logic leaving your controllers to deal mainly with processing form inputs and page flow.

Within the repositories I map LinqToSql classes and fields to domain models and then use the domain models within the service layer, controllers and views. For a larger system the extra layers will prove their worth in the long run.