MVC .Net

[guest2013-1]

I've been playing around with the idea of implementing this as an upgrade at work for our system. One requirement we have is that we'd like the ability to deploy per module (or change to a page) , instead of deploying the entire project.

Any idea if MVC allows you to deploy per module/page instead of the ENTIRE project? If yes, how?

Ta

 

[jeanres]

You can use a modular architecture as described here and here

First result in google.

 

[guest2013-1]

guess i need to lurn gewgle bettar

 

[Toitjie]

The answer is yes!

Views/pages are generated when they are referenced(ie. run time) by the user (ie when they browse to the page using a link, etc).

And because of that you can easily replace views without deploying the whole site.

However when one of the models/controllers change you will need to rebuild the project and deploy the bin.

 

[guest2013-1]

Okay cool. It looks like the "plugin" thing is the direction to go. We can bulk one specific module of our site into 1 DLL (which can be in its own project, which is nice) and then just copy that one DLL into the plugin folder when it changes. Makes handling things much easier and we can version control better. Plus having multiple developers work on their own modules causes less disruption overall when someone updates the wrong thing that affects the entire site.

Nice to know views can be replaced like that. Now I need to get cracking on an overall framework and do a proof of concept

 

[guest2013-1]

I see MVC 4 has a better grip on the modular thingy, going to test that and see if it helps with what I want