Software stack for convention based ASP.NET MVC development

Besides ASP.NET MVC's obvious conventions, what libraries do you take advantage of that minimize boot strapping, mapping objects, data access and such? I want to spend more energy developing domain logic as opposed to dealing with the details of object per开发者_如何学运维sistence (for example).

I have used StructureMap and NHibernate in the past to great effect. Are there other tools or other libraries I should consider that further streamline the process?

---

You can check out this example: http://whocanhelpme.codeplex.com/ (it is based on S#arp Architecture framework). I haven't actually tried it but I do use a lot of the mentioned libraries myself, and it got very good feedback in S#arp google groups.

---

You can write own core of project using:

• NHibernate - data access
• StructureMap - IoC, bootstrapping
• ...

that like you want or simply use one:

S#arp Architecture

---

We are very, very happy users of Autofac, NHibernate + FluentNHibernate :-) But to switch from StructureMap to Autofac or vice verca does not make difference. One of the next libraries I like to check out is AutoMapper.

FluentNHibernate + Schema generation is very worthwhile.

---

From my perspective and from long-time experience at .NET & .NET Core projects I recommend:

• Entity Framework for DAL (MS), sure with code-first (Microsoft)
• AutoMapper for copy and move data across DAL & BLL
• FluetValidation for check Input data, validation

together with:

• Dependecy injection for better architecture and solving using application services (Microsoft)
• Serilog for logging and running diagnostics