CODEWITHSUNDEEP
asp.net-mvcasp.net-mvc-3asp.net-mvc-areas
cfs
cfs

Reputation: 1324

How to seperate MVC project to several smaller MVC projects

I have an MVC 3 app that has some core functionality (most important is autorisation) but mainly serves as a portal to different areas or modules. I want to organize thit to different modules that with minor changes also can be deployed as their own website.

The project consists of a Forum, Blog engine, Messaging between users + 4-5 upcoming modules.

I looked at ScottGu's blog about MVC 2 and found something that seemed perfect:

enter image description here

Depending og what the customer need I want to only give them the exact modules they can use. It is also easier from a maintainence view to be able to work and update referencd assemblies in each project and just do a full update for the customers that have that spesific module on their server.

But in MVC 3 there is no apparent way to use Areas this way, do you know how?

Status I will try to add MVCContrib Portable areas to my existing solution and convert my areas ower and will post back the results. If it works I will mark it as the accepted solution.

Upvotes: 3

Views: 1770

Answers (2)

Adam Tuliper
Adam Tuliper

Reputation: 30152

This is possible in MVC3: From: http://bob.archer.net/content/aspnet-mvc3-areas-separate-projects

Right click on the shell project and "Add Area...". Type in the area name. This will create an Areas folder with your area in it. (This is not 100% needed but you do need the "Areas" folder and you can steal the XXXXAreaRegistration class for your application.)

Create a new MVC3 empty project in your solution to match your area. Move the XXXXAreaRegistration.cs file from the shell mvc project to the new project and adjust the namespace as applicable. (Or you can manually create an area registration class, it's a pretty simple class. Just use the Add area template generated one as an example.)

Edit the routes in the AreaRegistration folder as needed.

Delete the folder under the areas folder that the template wizard added.

Modify the web.config of the new project and take out the connection strings and the authentication, membership, profile, rolemanger sections. You will not need to deploy this web.config but the razor intellisense doesn't work without it during dev time.

Delete the global.asax file from the area's project or you will get extra default routes.

Create a virtual directory in the "Areas" folder of the shell project with the name of your area as the alias and point it to your "area" project. You will need to use IIS or IIS Express for this. I use IIS. For IIS Express you can use the appcmd.exe in the IIS Express folder or you can edit the applciationhost.config file.

Upvotes: 0

Daniel A. White
Daniel A. White

Reputation: 190897

MVCContrib has portable areas.

http://mvccontrib.codeplex.com/wikipage?title=Creating%20a%20Portable%20Area&referringTitle=Documentation

Upvotes: 3

Related Questions