Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have to code a web portal that offers multiple and varied features such as: notification and resolution of user problems, purchasing requests, requests for supplies, facilities management …
I thought I should create an MVC application and divide it by creating an area for common things and a separate area for each of the other features, but do not know whether the concept of area is suitable for my needs or is intended for other needs.
Thanks for your answers.
Areas will separate parts of your site into directories where each area/folder has their related views and controllers.
Areas also help separate your application in the URL structure.
I don’t think there is a hard rule of when to use Areas and when not to, most commonly though I would say it depends on the size of your application. A site with only a few pages would not realy need any areas, that might be overkill in design.