ASP.NET MVC如果我招谁惹先学的WebForms？ [英] ASP.NET MVC Should I bother learning webforms first?

问题描述

我即将进军的ASP.NET Web开发，我已经知道了一些使用的Visual Web Developer和一些Web表单的实现非常基本的。然而，而不是继续下去Web窗体路径和掌握VIEWSTATE和所有伴随着它的丑陋，我决定走了MVC的路线。

在这一点上，我想知道，我应该继续学习Web窗体，然后移动到MVC？或者，可以将MVC不知道有关Web窗体的事情独立学到了什么？什么是我最好的行动方针？

解决方案

没有，甚至不看Web窗体。

MVC建模更接近HTTP如何工作，这使得它更容易继续努力，打造当今的客户端脚本的Web应用程序。结合Web窗体和JavaScript真的是一种痛苦。

MVC是还在于它有助于得到服务器侧结构的权利要好得多。它可以使用一个模型 - 视图 - presenter（或控制器）分离的Web窗体过，但对Web窗体顶部显示为躲开了录音。

最后，你将与MVC启动时都几乎没有使用任何的WebForms知识。这是相当的其他方式，我教过的MVC开发的WebForms必须从WebForms的去洗脑第一; - ）

I'm about to foray into ASP.NET Web Development and I already know some of the very basics using Visual Web Developer and some of the implementations of Web Forms. However, instead of continuing to go down the Web Forms path and mastering VIEWSTATE and all of the ugliness that comes along with it, I've decided to go the MVC route.

At this point, I'm wondering, should I continue to learn Web Forms and then move over to MVC? Or can MVC be learned independently without knowing a thing about Web Forms? What's my best course of action?

解决方案

No, don't even look at Web Forms.

MVC is modeled much closer to how HTTP actually works, which makes it much easier to work with and to build today's web applications with client side scripts. Combining Web Forms and javascript is really a pain.

MVC is also much better in that it helps getting the server side structure right. It is possible to use a model-view-presenter (or controller) separation on Web Forms too, but it has to be ducked taped on top of Web Forms.

Finally, you will have nearly no use of any WebForms knowledge when starting with MVC. It's rather the other way around, the WebForms developers I've taught MVC have to be de-brain-washed from WebForms first ;-)

这篇关于ASP.NET MVC如果我招谁惹先学的WebForms？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！