NickName:Gopinath Ask DateTime:2009-07-29T21:51:36

Multiple ASP.NET MVC projects that builds as single ASP.NET MVC Application

We want to split our large asp.net mvc web application into multiple Visual Studio projects so that each team can independently on their visual studio project.

Desired structure is:

ASP.NET MVC application that is responsible for the base UI
Module 1 - VS Project (Does this need to be a ASP.net MVC App or .dll?)
Module 2 - VS Project (Does this need to be a ASP.net MVC App or .dll?)
so on....

Each module should contain it's own controller & views that are responsible for functioning of the module. T

How to split the ASP.NET Application in to multiple projects and then merge them as a single website during build process?

Copyright Notice：Content Author:「Gopinath」，Reproduced under the CC 4.0 BY-SA copyright license with a link to the original source and this disclaimer.
Link to original article：https://stackoverflow.com/questions/1200424/multiple-asp-net-mvc-projects-that-builds-as-single-asp-net-mvc-application

Answers

Darin Dimitrov 2009-09-01T14:04:32

ASP.NET MVC V2 has a feature called Areas which allows you to have separate projects referenced by the main application. Check out ScottGu's post.",

Gopinath 2009-09-01T13:53:19

The problem is sorted out by just creating multiple MVC projects and merging the output at the end by simple copy & paste :)\n\nhere is the structure we followed:\n\n\nMyApp.Web.Shell (just contains themes, css, js & images required for the web app)\nMyApp.Web.Home\nMyApp.Web.UserManagement\nMyApp.Web.DeviceManagement\nMyApp.Web.ContentManagement\n.....etc...\n\n\nAt the end we are using build scripts to merge output of all the projects and generate the files required for the total web app to run. \n\nIf you need any help in implementing similar solution, get in touch with me at link text",

JaredPar 2009-07-29T15:18:47

One tool you may be interested in looking at is called ILMerge\n\nhttp://research.microsoft.com/en-us/people/mbarnett/ilmerge.aspx\n\nThis is a tool that will allow you to merge several .Net assemblies into a single DLL. It could be used to combine the output of your several projects into a single DLL for deployment.\nI haven't ever tried it with Asp.Net MVC and I'm not familiar enough with the MVC architecture to say whether or not it will work for your situation. But it's likely worth a try.",

Sachin Chavan 2009-09-19T05:24:16

Follow this link it will solve you problem.\n\nTakes just 10 mins to complete the walk-through.\n\nWalkthrough: Organizing an ASP.NET MVC Application by Logical Areas",

Kevin Jones 2009-09-01T14:01:11

One way we handled this in my previous job was to build a master 'controller' application. This app was deployed and was public facing. It's job was to read the incoming URL and, based on a bunch of mapping rules in config files, map that URL to other MVC applications running on the same server. This gave us lots of options such as being able to run the backing apps on different servers in the farm if we wanted to do crude load balancing. You need to manage things such as authentication across the multiple apps (if you're using authentication).\n\nThis basically gives you the ability to have as many different MVC apps as you need running on the servers all with the same front controller (essentially)",

MunkiPhD 2009-09-01T14:04:39

You could just use good Source Control and have the respective teams check out what they need to work on. \n\nThis way you have only one dll at compile time...",