Last post Feb 25, 2010 01:33 AM by HeartattacK
Feb 25, 2010 12:02 AM|vijayst|LINK
Web server controls should work the same way in MVC application. I know ViewState and architecture is different. But making a tag work just involves giving a new file extension and creating a DLL to handle it?
Feb 25, 2010 01:27 AM|HeartattacK|LINK
Server controls that don't rely on viewstate, controlstate and postbacks work perfectly fine in MVC apps. And those that require those three - they go in the opposite direction of what MVC stands for. As such, they can't be supported. The whole point of
MVC is to remove the abstraction that webforms provides in hiding http fundamentals. Supporting controls that use viewstate, controlstate and postbacks goes against that completely.
Feb 25, 2010 01:33 AM|HeartattacK|LINK
I see that you are spreading a bit of misinformation in your blog. Your statements suggest that there are no cool controls for MVC developers. On the contrary, there are quite a few. The MvcContrib project for example has an awesome Grid helper. Telerik
has some great MVC extensions. And you can very easily create your own html helper (which are far far easier to create than custom server controls). You say that none of Ajax toolkit controls are usable in asp.net MVC. The truth is that the Ajax toolkit has
been integrated into the asp.net Ajax Library and is very simple to use in purely client side format. By the way, the Ajax toolkit has always been available in scripts only format to support use in plain html, php or any other technologies. The latest (beta)
release just makes it that much easier to use.
Lastly, you say there're no contol's like TextBox, DropDownList etc. How is:
<asp:TextBox runat='server' id='txtName' />
a control and
<%= Html.TextBox("Name") %>
not a control?