Are areas a good organizational feature, or just extra work?

Posted by SOfanatic on Programmers See other posts from Programmers or by SOfanatic
Published on 2013-08-02T12:28:40Z Indexed on 2013/08/02 16:02 UTC
Read the original article Hit count: 154

Do Areas in ASP.NET MVC end up being a help or just a drag in the end (because of the URL construction)? Would it be better to have subdirectories inside the main Controllers folder? or are there any other options to organizing a project?

EDIT

For example, this is your average link without Areas:

@Html.ActionLink("Home","Index","Home")

and this is your average link with Areas:

@Html.ActionLink("Home","Index", new { Area = "", Controller = "Home"})

Could the following work? (Main controller with subdirectories)

Main controller with subdirectories

I'm just trying to find out if implementing Areas in a project is worthwhile, because I also read that it can be problematic when using Dependency Injection. And is there an alternative to Areas?

© Programmers or respective owner

Related posts about c#

Related posts about architecture