Question

I want to start new application on ASP.NET MVC4 using different different approach like domain driven development , design patterns , dependency injection , Entity Framework as ORM etc.

Need some advice on what should be the starting point of development? Should I start with first relationships of classes or start with traditional approach?
e.g there are three module.

1. User Management.
2. Logging.
3. Error Logging.

Should I first complete with user management like domain classes then its services and then its CRUD operations in actual web application? and after that …will start with logging (same process as mention in user management). and then in error logging as well.

So What are best practices to start development using those kind of concept or tools?

Answer 1

ASP.NET MVC4 is just a presentation part of solution. With Domain-Driven approach you start with domain (usually separate library project) and then add presentation (web site, desktop application etc) and persistence (implementation of repository and uof interfaces declared in your domain).

So, you start with creating domain model (not whole, but part of that). Then in any order you create UI which uses you domain model, and implementation of repositories for persisting your domain model via Entity Framework. Well actually views should use ViewModels (otherwise your POCO domain objects will be polluted with Data Annotations attributes and other stuff). It’s a controller part where you will use domain model. Also you will inject repository implementations to controllers via dependency injection.