I'm currently learning ASP.Net MVC; I'm using Visual Studio Express 2012 with MVC4 (which is the last version) and I'm totally new to this stuff. My goal is to rewrite a huge web application to MVC, so I was told to separate my main solution into 3 projects using the code-first method: The core (models and controllers I guess) The UI (views, scripts, and Content) And the Database (Entity Framework 5.0 will be used) I'm quite familiar with MVC, but not separating stuff into different projects. Now I'm a bit lost, I don't have a clue on how to do that, which should reference who, where, how, etc.

Your solution could be structured this way: UI - ASP.NET MVC application project containing the controllers, views, view models, mapping logic between your domain models and view models, scripts, styles, ... DAL (EF 5.0, EF autogenerated domain models, Data Contexts, ...) everything that is specific to the data retrieval The UI layer will then reference the DAL layer. Some people might also opt to externalize the controllers, view models and mapping logic into a third layer which in turn will reference the DAL layer. The UI layer in this case will reference both other layers.

asp.net-mvc

Titouan D.

Reputation: 476

Separate solution into different projects

I'm currently learning ASP.Net MVC; I'm using Visual Studio Express 2012 with MVC4 (which is the last version) and I'm totally new to this stuff. My goal is to rewrite a huge web application to MVC, so I was told to separate my main solution into 3 projects using the code-first method:

The core (models and controllers I guess)
The UI (views, scripts, and Content)
And the Database (Entity Framework 5.0 will be used)

I'm quite familiar with MVC, but not separating stuff into different projects. Now I'm a bit lost, I don't have a clue on how to do that, which should reference who, where, how, etc.

Upvotes: 8

Answers (3)

sathishkumar

Reputation: 1816

create an empty solution using the Visual Studio Blank Solution template

add a solution folder (folder name will be your project name)

then right click that folder and select add project then select "class library" (for The c# classes domain logic)

same again right click the folder and select add project then select asp.net mvc3 template

then same way you create the test template as a new project.

For more information you can follow this book http://www.apress.com/9781430234043

Upvotes: -1

Darin Dimitrov

Reputation: 1039438

Your solution could be structured this way:

UI - ASP.NET MVC application project containing the controllers, views, view models, mapping logic between your domain models and view models, scripts, styles, ...
DAL (EF 5.0, EF autogenerated domain models, Data Contexts, ...) everything that is specific to the data retrieval

The UI layer will then reference the DAL layer.

Some people might also opt to externalize the controllers, view models and mapping logic into a third layer which in turn will reference the DAL layer. The UI layer in this case will reference both other layers.

Upvotes: 3

Rob

Reputation: 3574

There are tutorials available on here: http://www.asp.net/mvc It really helped me out to get the basics of MVC, but be aware - sometimes there are parts missing in the video's, but you can find the code which isn't provided easily elsewhere.

Good luck :)

The tutorials are used to show code first.

Upvotes: 0

Separate solution into different projects

Answers (3)

Related Questions