Click here to Skip to main content
Click here to Skip to main content

Using areas in ASP.NET MVC to organize a project

, 3 Jun 2013
Rate this:
Please Sign up or sign in to vote.
How to organize an ASP.NET MVC project using areas.

Introduction

When we work with ASP.NET MVC, we find some default folders (view, model, controller, and some more), but if the application is big, it is complicated to maintain a structure logic for the files and modules for the site. To solve this problem, ASP.NET MVC provides a powerful feature called areas, with areas it is possible to "isolate" the modules of your site.

Using the code

First step: create a new ASP.NET MVC 4 application, I recommend to use the basic template.

Next step: Over the project name, right click -> Add -> Area, and assign a name to the new area, when the area creation ends, we see a new folder called Areas, and within this folder you can see a folder with the name of your area and some files, think that an area is a mini-MVC project within your principal project.

The next image shows how it looks if you create an area called Reportes:

An important file that is created too, is ReportesAreaRegistration.cs, this file is used to configure the routing system for the area.

public override void RegisterArea(AreaRegistrationContext context)
{
    context.MapRoute(
        "Reportes_default",
        "Reportes/{controller}/{action}/{id}",
        new { action = "Index", id = UrlParameter.Optional }
    );
}

Also, in Global.asax, on the Application_Start method the configuration for the areas is called:

AreaRegistration.RegisterAllAreas();

Now, if you run the application, you received an error that says:

The request for ‘Home’ has found the following matching controllers:
Areas.Areas.Reportes.Controllers.HomeController
Areas.Controllers.HomeController

This error is produced because you have two controllers with the same name, but the solution is easy, go to the function RegisterRoutes of the class RouteConfig and add a namespace:

routes.MapRoute(
    name: "Default",
    url: "{controller}/{action}/{id}",
    defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional },
    namespaces: new[] { "Areas.Controllers" }
);

I hope this post will be useful for you!

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

julitogtu
Software Developer (Senior) BDotNet
Colombia Colombia
Microsoft ASP.NET MVP, I love software development, especially web development, I have worked with Microsoft technologies for about five years in the development of large scale enterprise applications, co-creator of several Carreras for the Microsoft Virtual Academy (MVA), speaker at events Microsoft Colombia and member of the Core Group BDotNet community. You can see some of my contributions in http://julitogtu.com/
Follow on   Twitter   LinkedIn

Comments and Discussions

 
Generalnice quick explanation PinmemberMember 1029511527-Sep-13 0:38 
QuestionAreas are a bad move Pinmemberjphamilton3-Jun-13 6:12 
AnswerRe: Areas are a bad move PinmemberMember 85284093-Jan-14 9:12 
AnswerRe: Areas are a bad move Pinmemberlukasz.f9-Apr-14 5:43 
GeneralMy vote of 4 Pinmemberasp_crazy_guy2-Jun-13 23:07 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Mobile
Web04 | 2.8.140721.1 | Last Updated 3 Jun 2013
Article Copyright 2013 by julitogtu
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid