blocks|key|2930509|text|这就是MVC的伟大之处。它的工作原理比普通的ASP.NET表单更接近于框架的基础。因此，通过使用MVC并理解它，您将更好地理解WebForms是如何工作的。WebForms的问题是有很多神奇的东西，花了大约6年的时间才能让Web像Windows+Forms一样工作，所以你有了控件树层次结构和所有转换到Web上的东西。使用MVC，您可以获得核心，而不受WinForm的影响。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2930510|因此，从MVC开始，如果需要的话，您将能够很容易地迁移到WebForms。|2930511|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Here is the great thing about MVC. It works closer to the base of the framework than normal ASP.NET Web Forms. So by using MVC and understanding it, you will have a better understanding of how WebForms work. The problem with WebForms is there is a lot of magic and about 6 years of trying to make the Web work like Windows Forms, so you have the control tree hierarchy and everything translated to the Web. With MVC you get the core with out the WinForm influence.

So start with MVC, and you will easily be able to move in to WebForms if needed.

blocks|key|717888|text|我同意Nick的观点:+MVC更接近于真正的web范例，使用它你将会面对你的网站是如何真正工作的。WebForms会让你远离这些东西，我觉得这真的很违反直觉。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|717889|我建议你直接跳到MVC，跳过WebForms。如上所述，如果需要，您将能够重新使用它。|717890|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I agree with Nick: MVC is much closer to the real web paradigm and by using it you'll be confronted with how your website really works. WebForms astracts most of these things away from you and, coming from a PHP background, I found it really anti-intuitive.

I suggest you directly jump to MVC and skip WebForms. As said, you'll be able to get back to it if needed.

blocks|key|3775676|text|与ASP.Net+ASP.NET相比，MVC是对基础框架的完全不同的抽象。与ASP.NET+Webforms相比，使用MVC可以更好地控制幕后发生的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3775677|在我看来，学习不同的方法通常会让你成为一名更好的程序员，但在这种情况下，可能会有更好的东西需要学习。|3775678|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

ASP.Net Webforms is a completely different abstraction over the base framework than ASP.NET MVC. With MVC you've got more control over what happens under the covers than with ASP.NET Webforms.

In my opinion learning different ways to do things will usually make you a better programmer but in this case there might be better things to learn.

blocks|key|5186629|text|ASP.NET+MVC是为希望将客户端代码与服务器代码解耦的开发人员而设计的。我一直想写JavaScript，XHTML，CSS客户端，可以从一个服务器移动到另一个服务器(不考虑服务器技术)。客户端的安装和完成非常耗时，因此您可能希望在尽可能多的服务器上使用它们(和子组件)。此外，这种解耦允许您的服务器支持任何支持HTTP和尖括号(和/或JSON)的客户端技术，如WPF/Silverlight。没有了MVC，你不得不与整个ASP.NET团队产生敌意-但Scott+Guthrie是一个很酷的家伙，他把MVC带到了谈判桌上，他的前任们(也许还有Scott自己)多年来几乎完全专注于让ASP.NET窗体程序员编写web应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5186630|在使用ASHX之前，我主要基于ASP.NET文件构建ASP.NET应用程序-HTTP处理程序。我可以向你保证，任何“真正的”微软商店都不会鼓励这种行为。从(明智的)管理角度来看，规定所有开发人员使用供应商推荐的方式来使用供应商的工具会更容易。因此，落后一到两年的IT商店将要求您了解MVC之前的工作方式。当您有一个“遗留”系统需要维护时，这也会派上用场。|5186631|但是，对于绿色领域，它完全是MVC！|5186632|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

ASP.NET MVC is for developers who desire to decouple the client code from the server code. I have wanted to write JavaScript, XHTML, CSS clients that can move from server to server (without regard to server technology). Clients are time-consuming to fit and finish so you would want to use them (and sub-components) for as many servers as possible. Also this decoupling allows your server to support any client technology that supports HTTP and angle-brackets (and/or JSON) like WPF/Silverlight. Without ASP.NET MVC you were forced into a hostile relationship with the entire ASP.NET team---but Scott Guthrie is a cool dude and brings MVC to the table after years of his predecessors (and perhaps Scott himself) almost totally focused on getting Windows Forms programmers to write web applications.

Before ASP.NET MVC, I built ASP.NET applications largely based on ASHX files---HTTP handlers. I can assure you that no "real" Microsoft shop would encourage this behavior. It is easier from a (wise) management perspective to dictate that all your developers use the vendor-recommended way of using the vendor's tools. So IT shops that are one or two years behind will require you to know the pre-MVC way of doing things. This also comes in handy when you have a "legacy" system to maintain.

But, for the green field, it's MVC all the way!

blocks|key|5186467|text|这取决于你的动机。如果您打算将自己推销为一名ASP.NET开发人员，那么您将需要这两种工具。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5186468|如果这只是为了您自己的乐趣，那么请转到MVC。|5186469|我个人的感觉是webforms还会存在好几年。所以很多人都有时间和精力投入到他们身上。然而，我认为人们会慢慢地(或者可能不会那么慢！)迁移。Webforms一直只是一种让拖放式VB4+morts思考web开发的方法。它有点起作用了，但它确实夺走了很多控制权。|5186470|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

It depends on your motivations. If you're going to sell yourself as an ASP.NET developer, you will need both.

If this is just for your own pleasure, then go to MVC.

My personal feeling is that webforms will be around for quite a few years more. So many people have time and energy invested in them. However, I think people will slowly (or maybe not so slowly!) migrate. Webforms was always just a way to get drag-and-drop VB4 morts to think about web development. It kindof worked but it does take away alot of control.

blocks|key|5186296|text|与MVC相比，在正常的web表单场景中有更多的陷阱。视图状态和数据绑定有时会很棘手。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5186297|但对于MVC来说，这只是简单的表单post/呈现老式的方式。并不是说它不好，它只是不同，而且更干净。|5186298|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

IMO, there are more pitfalls in normal web forms scenarios than with just MVC. Viewstate and databinding can be tricky at times.

But for MVC, it's just plain simple form post/render things old-school way. Not that it is bad, it is just different, and cleaner too.

blocks|key|2930675|text|我真的不能从技术上谈论MVC和“传统”，因为到目前为止我只使用了传统模型。根据我所读到的，我不认为其中一个比另一个优越得多。我认为一旦你“明白了”，你就可以在这两个方面都非常有效率。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2930676|实际上，我会考虑到大多数书籍、代码样本和现有的应用程序都是为“传统”方式编写的。你有更多可用的帮助，你的技能将对以“传统”方式编写现有应用程序的雇主更有用。|2930677|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I can't really speak technically about MVC vs "traditional" as I have only used the traditional model so far. From what I have read though, I don't think one is vastly superior to the other. I think once you "get it", you can be very productive in both. 

Practically though, I would take into consideration that most books, code samples and existing applications out there are written for the "traditional" way. You have more help available and your skills will be more useful for employers with existing applications written in the "traditional" way.

blocks|key|3775998|text|如果您不知道如何使用或没有使用原始级web请求/响应和原始html/css渲染的经验，那么MVC将是一个很好的起点。然后，您将更好地理解webforms和mvc的优缺点。它们都将在未来出现，因为它们都满足了不同的需求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3775999|虽然我会说webforms是一个高度滥用和滥用的平台。如此多的“看不到代码”的垃圾给所有使用它的人带来了坏名声。花时间去理解它并正确地使用它，你会发现它是一个非常可扩展和健壮的平台。|3776000|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you don't know how or haven't has experience with raw level web request / response and raw html/css rendering then MVC will would be good place to start.
You will then better understand the pros and cons of both webforms and mvc. They will both be around in the future as the both address different needs. 

Though I will say webforms is a highly misused and abused platform.
So much of the "look no code" rubbish gives all who use it a bad name.
Put in the time to understand it and use it properly you'll find its a very extensible and robust platform.

As someone with some winforms and client applications experience - is it worth going back and learning the way traditional ASP .NET pages work, or is it okay with moving straight into ASP .NET MVC?

I'm kind of looking for pitfalls or traps in my knowledge of general C#, that I won't know from the screencast series and things on the ASP .NET site.

Traditional ASP .NET Web Forms vs MVC

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

对于一些有winforms和客户端应用程序经验的人来说--是否值得回到过去学习传统的ASP页面的工作方式，或者直接进入ASP .NET是可以的吗？我在寻找我的通用C#知识中的陷阱或陷阱，我不会从屏幕视频系列和ASP .NET站点上知道的东西。

问传统ASP与.NET
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问传统ASP与.NETEN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问传统ASP与.NET
EN