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:
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?
It shouldn't! That's why it's designed in a modular way. In most web applications out there, we version and deploy all these assemblies (Web, BLL and DAL) together. So, separating a project into 3 projects does not add any values.
ASP.NET - Single-Page Applications: Build Modern, Responsive Web Apps with ASP.NET. Single-Page Applications (SPAs) are Web apps that load a single HTML page and dynamically update that page as the user interacts with the app.
Luckily, the answer is yes. Combining ASP.NET Webforms and ASP.NET MVC in one application is possible—in fact, it is quite easy. The reason for this is that the ASP.NET MVC framework has been built on top of ASP.NET.
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.
The problem is sorted out by just creating multiple MVC projects and merging the output at the end by simple copy & paste :)
here is the structure we followed:
At 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.
If you need any help in implementing similar solution, get in touch with me at link text
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With