blocks|key|577097|text|你使用web表单的理由是有道理的:快速原型化，在客户面前获得模拟用户界面。另一个原因是大量的供应商提供服务器控件来转储到web窗体页中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|577098|我个人认为，对于那些习惯于使用拖放设计器而不是手动编辑HTML的人来说，MVC有一点学习曲线。也就是说，一旦你克服了它，我相信你再也不会使用web表单了。弹出了许多控件，它们可以很好地与MVC一起工作。Telerik's+MVC+Extensions只是一个例子，恰好也是开源的。|offset|length|577099|entityMap|0|LINK|mutability|MUTABLE|url|http://www.telerik.com/products/aspnet-mvc.aspx^0|0|2T|O|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Your reasons for using web forms are valid: rapid prototyping to get mock UI in front of a client. The other reason would be the huge number of vendors who offer server controls to dump into web forms pages.

I personally think MVC has a bit of a learning curve for those who are used to having a drag-n-drop designer rather than editing the HTML by hand. That said, once you get past it I don't believe you'd ever use web forms again. There are a lot of controls popping up that work very nicely with MVC. <a href="http://www.telerik.com/products/aspnet-mvc.aspx" rel="nofollow">Telerik's MVC Extensions</a> are just one example, that happens to be open source as well.

blocks|key|577121|text|在某些情况下，您回退到页面回发，这意味着您实际上维护了两个不同的模型。一个在客户端，一个在服务器端。在回发的情况下，您在服务器端进行了更改，现在您需要找到一种方法将这些更改传达给客户端。我不知道您是如何做到这一点的，但这不是完全可扩展的，因为每个更改都必须在客户端和服务器端之间同步。在MVC中，我们使用服务器端视图模型来处理这一点，这些模型在客户端由框架自动处理。(在顶部，我们使用客户端绑定库，如Knockoutjs，与MVC一起使用要比使用webforms容易得多)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|577122|其次，在webforms中，您也没有获得路由优势。所以你的路由仍然看起来像那些丑陋的Mysite.com/mypage.aspx。|577123|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|$]]

You fallback to page postback in certain cases, this means that you are actually maintaining two different models. One at the client side and one at the server side. In case of the post back, you make the changes at the server side and now you need to find a way to communicate that changes to the client side. I don't know how you are doing this but this is not entirely scalable because every change has to be synced in between client side and server side both. In MVC we take care of this using server side View Models which are automatically taken care at the client side by the framework. (On top we use client-side binding libraries like Knockoutjs, which are far more easier to use with MVC than webforms)

Secondly you don't get the routing advantages too in webforms. So you routes still look those ugly Mysite.com/mypage.aspx.

blocks|key|2197116|text|我在这里有一个房地产应用:+www.homevana.com。这是一个web表单应用，但我打赌你不会知道的。对于这个项目的需求，客户端繁重的应用程序在有大型复杂表单要完成的时候仍然使用web表单来收集关于待售房屋的数据是最佳选择。因此，Homevana应用程序上的大多数.aspx页面都没有后置代码，但是当有复杂验证的表单时，我使用带有服务器控件的.aspx页面和Peter+Blum的验证套件：http://www.peterblum.com/Home.aspx+(当然都是复杂的客户端验证)来快速完成这方面的工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2197117|可以通过nuget：http://www.hanselman.com/blog/IntroducingASPNETFriendlyUrlsCleanerURLsEasierRoutingAndMobileViewsForASPNETWebForms.aspx安装FriendlyUrl包很容易摆脱“丑陋的”.aspx扩展，不过也可以使用一个IIS7正则表达式url路由规则来完成。|2197118|这一切都是关于合适的工具来完成这项工作。MVC非常棒，我还有很多其他使用MVC的项目，但它并不总是满足项目需求的最佳工具。|2197119|entityMap|0|LINK|mutability|MUTABLE|url|http://www.peterblum.com/Home.aspx|1|http://www.hanselman.com/blog/IntroducingASPNETFriendlyUrlsCleanerURLsEasierRoutingAndMobileViewsForASPNETWebForms.aspx^0|5I|Y|0|0|A|3B|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

I have a real estate app here: www.homevana.com. This is a web forms app but I bet you wouldn't know it. For the requirements of this project, a client heavy app that still utilized web forms at times when there was large complex forms to complete to gather data about the home for sale was the sweet spot. So most .aspx pages on the Homevana app have no code behind but when there are forms with complex validation I used .aspx pages with server controls and Peter Blum's validation suite: <a href="http://www.peterblum.com/Home.aspx" rel="nofollow">http://www.peterblum.com/Home.aspx</a> (all complex client side validation of course) to rapidly get that aspect of the job done. 

The FriendlyUrl package that you can install via nuget: <a href="http://www.hanselman.com/blog/IntroducingASPNETFriendlyUrlsCleanerURLsEasierRoutingAndMobileViewsForASPNETWebForms.aspx" rel="nofollow">http://www.hanselman.com/blog/IntroducingASPNETFriendlyUrlsCleanerURLsEasierRoutingAndMobileViewsForASPNETWebForms.aspx</a> gets rid of that "ugly" .aspx extension easily though you can do it with one IIS7 regex url routing rule too.

It is all about the right tool for the job. MVC is awesome and I have many other projects where I use MVC but it isn't always the best tool for the requirements of the project.

When recently designing a medium to large scale web app, I decided to go with a client-heavy implementation of webforms rather than asp.net MVC for the UI layer. 

The reason being that with webforms it is easy to quickly knock up screens and glue together a web app (I use Telerik's radcontrols extensively as they have a rich client model). I find that the earlier I get a prototype UI infront of a client, the quicker they can look at it and evolve it into what they really want.

When I say client-heavy webforms, I mostly bind data client-side and then use web services to handle events from the client - the web services interact with my business layer and deal in JSON. The advantage comes when, say, one UI event requires that many controls be updated - I can then fall back on the asp.net page cycle and fire off a partial-postback having wrapped the various controls in update panels.

The way I see it, I can have my cake and I can eat it! I can use lightning-fast JSON web services for performance critical areas of my app but I can revert to the postback/partial postback model for complex UI areas. All in all, less development time and performant where it matters.

So finally, a question!

I'm not trying to resist MVC just simply asking is it better than what I'm doing above and if so, why?

asp.net mvc vs client-heavy webforms

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

当最近设计一个中到大型的web应用程序时，我决定使用以客户端为主的webforms实现，而不是UI层的asp.net MVC。原因是，使用webforms可以很容易地快速打开屏幕并将web应用程序粘合在一起(我广泛使用Telerik的radcontrols，因为它们有一个富客户端模型)。我发现，我越早在客户面前得到一个...

问asp.net mvc vs客户端繁重的webforms
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问asp.net mvc vs客户端繁重的webformsEN