Developer Forum »
How important is MVC support?
181 posts

We're working on implementing support for MVC templates in Webnodes. How important is this for you? Do you think you will switch completely for all new projects, or do you think you'll make a decision on a project to project bases?

58 posts

After having worked with ExtJS/Webnodes for a while now, I'm not a 100% dependent upon MVC support, but almost every ASP.NET/Ext JS developer out there is recommending MVC and not Webforms in combination with Ext and similar JavaScript frameworks.

The big upside is cleaner application structure, cleaner code and guaranteed increased productivity once the developer is up and running in the technology.

On general basis I want to use MVC no matter what, because it gets me back to "basics", leaving all the desktop-stuff behind which Webforms was designed to deliver for web. It forces me to separate concerns, it's more JavaScript-friendly and more testable.

Having said that, developing large applications with complex forms might be a bigger job in MVC than Webforms (I'm not sure), so it might be a good idea to consider each option for what kind of project you're going into. As with all technologies there are always upsides and downsides...

But the whole idea of switching to MVC entirely is very tempting! :)

2 posts

In my opinion it's important in more than one way to support MVC.  From a community view point it broadens the appeal of the Webnodes platform by opening up to the significant part of the market that has already made a complete switch from Webforms to MVC. 

From a personal point of view it would serve as a huge advantage to be able to choose between webforms and MVC on a project to project basis with MVC presenting itself as the way to go in most projects.

Hurry up with the MVC support! :)

1 posts

Hey - have you started this yet, i'd be very interested in this for a project i'm working on now!

 

Cheers.

181 posts

We've started implementing MVC support, but it's not finished yet. Our current plans aims for a release before christmas.

1 posts

MVC rules, and more importantly our MVC App rules, as we wouldn't be building on top of an outside framework. 

I find myself in need of a CMS system, but it has to be outside of the application.  Content managment and delployment are most important, and the presentation layer has to be internally owned.  

I haven't seen your MVC approach yet, but I do hope that it lends itself to my app pulling in stuff that you manange followed by my app doing the rendering.

I am looking forward to deeper reading.

 

1