Asp.net MVC 3 and NHibernate Architecture

Question

I setup a solution with the following structure:

Project.Core
- Domain
- Mappings
- Repositories
Project.Web
- Views
- Models
- Contollers

Project.Web is the asp.net MVC 3 template. I was wondering what would be the best architecture would be if i'm using MVC and NHibernate and I wont other web applications to utilize the Project.Core library.

It seems like the Domain and the Models are pretty much the same thing?

If I want to use the Domain's instead of the model how would I modify the asp.net mvc3 project to accept this?

Thanks

James Kovacs · Accepted Answer · 2011-03-30 22:07:44Z

1

Yes, your domain objects in Project.Core are the same as your models. Just delete your Models folder in Project.Web and create a project reference from Project.Web to Project.Core. Since Project.Core is simply a Class Library project and contains your domain model, repositories, and mappings*, you can use these classes from Project.Web, a console app, web service, or any other code.

answered Mar 30, 2011 at 22:07

James Kovacs

11.7k42 silver badges44 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Mike Over a year ago

Thanks James. I liked the recent presentation you gave on NHibernate 3.

Eatdoku Over a year ago

in mvc, the Model should be the data context of the view, i don't think it should be mixed with the domain objects.

Rushino Over a year ago

Yeah I prefer not to call this a model but instead a ViewModel or a PresentationModel which make the distinction between them and domain objets.

Thunder Over a year ago

We can't use data annotations , eg [Required] if we place the models in project.core.Am I right? or can it be done?

Collectives™ on Stack Overflow

Asp.net MVC 3 and NHibernate Architecture

1 Answer 1

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related