ASP.NET MVC framework - ready or not
Following a 1 hour presentation by Scott Hanselman and Eilon Lipton that I attended yesterday at Dev Connections
One of the key point to understand about the implementation of this framework is that it is a new behavior that is different than the regular web form (postback oriented) as it actually doesn't have viewstate and no postback usage,
This actually mean that if you would like to create an application you will not be able to use your current web controls and you would probably have to create the logic by your own (or wait for future vendor's implementation (in the demo we saw a very basic usage of old ASP style inline coding :( )
I asked Phil (PM of MVC) how would he implement a real life scenario application that holds few parts on the page (actually each part should have its own controller) and sadly he could not answer this yet (this is perfectly ok because this is not even a CTP) but sadly he said that in the near CTP that will be shipped at December we will not have support for sub controllers and this means that we would not be able to actually use it for more complex applications.
in general I think that this framework is in the very first stages and have a lot to evolve (and I guess it will change a lot in the future).
The above kinda make me think about the entire framework and I came a long of few points:
- Currently I don't think that in the next 6 months this framework will be able to be implemented on a real life application as I described above.
- I think the name should be changed to something like "RESTfull behaviors" (apparently Dino Esposito also think almost like me :) ) because that is the main concept presented and this drive the entire solution
- I think that there will have to be a change to the framework to allow it to connect (encapsulate) into existing pages and user controls and take advantage of the rich web controls.