转载:如何选择ASP.NET MVC 和 ASP.NET WEBFORM
2010-03-26 00:29
567 查看
图片出处:http://topic.csdn.net/u/20100111/14/36a773b7-8663-4694-a085-274bdd4317d9.html?55591
内容出处:http://blog.sina.com.cn/s/blog_533c03650100dxhh.html
1. Are you considering test-driven development (TDD)?
TDD enables you to write tests for an application first, after which the
application logic is developed. An ASP.NET Webforms application uses only
one class to display output and handle user input. Automated testing of this
class is complex as you are required to load the full ASP.NET stack into a
separate process (for example, in IIS). The MVC framework allows the testing
of each component separately, without requiring the full ASP.NET stack. For
example, you can test your model separately from your controller without
requiring a view. If you are considering TDD, the ASP.NET MVC framework
will be the better choice.
2. Is there a need for fine control over HTML markup?
ASP.NET Webforms automatically inserts hidden HTML markup, IDs,
JavaScript, and so on, into your page's HTML output because of its
event‑driven architecture and its use of ViewState. The ASP.NET MVC
framework allows for 100% control over the HTML output. If you require full
control over your HTML markup, the ASP.NET MVC framework will be the
better choice.
3. Is the application heavily data-driven?
If you are developing an application that is heavily data-driven and is using
grids or a lot of master-detail editing of data, ASP.NET Webforms may
be the better choice as it provides a lot of controls that will aid you in the
development of these kind of applications. Of course, you can use the
ASP.NET MVC framework for these tasks too, but you will be required to
write more code to achieve the same goal.
4. Is there a need for a Winforms-like development approach?
Does your development team write Winforms code? Is there a need for an
event-driven programming approach? In these cases, consider ASP.NET
Webforms in favor of ASP.NET MVC.
5. Is there a need for a rapid application development (RAD)
development approach?
Does your client expect a quick prototype of an application? Is the use of
drag-and-drop development using pre-created web controls required? If so,
consider ASP.NET Webforms in favor of ASP.NET MVC.
相关文章推荐
- 如何选择ASP.NET MVC 还是 ASP.NET WEBFORM
- ASP.NET WebForm Form表单如何实现MVC那种“自动装配”
- 经典技术文章转载:如何选择ASP.NET Web 服务与.NET Remoting
- ASP.NET WebForm Form表单如何实现MVC那种“自动装配”效果呢?
- asp.net mvc asp.net webform extjs jquery这些东西应该如何选择
- 【转载】正确认识WebForm与Asp.NET MVC
- (转载)Asp.net中如何将DataSet写入xml文件,及如何将xml读出来绑定到DataGrid 选择自 kgdiwss 的 Blog
- 正确认识WebForm与Asp.NET MVC (转载)
- 如何将项目添加到在ASP.net MVC的选择列表
- ASP.NET WebForm Form表单如何实现MVC那种“自动装配”效果呢?
- 新项目选择asp.net webform还是asp.net mvc?
- ASP.NET WebForm Form表单如何实现MVC那种“自动装配”效果呢?
- ASP.NET WebForm Form表单如何实现MVC那种“自动装配”效果呢?
- [转载]ASP.NET Web 服务还是 .NET Remoting:如何选择,使用 Microsoft .NET 建立分布式应用程序
- ASP.NET中如何让DropDownList控件既能做选择又能做输入用(转载)
- ASP.NET MVC 中如何处理 ASP.NET WebForm 或其他历史遗留的 URL
- 转载:正确认识WebForm与Asp.NET MVC
- 【转载】返璞归真 asp.net mvc (11) - asp.net mvc 4.0 新特性之自宿主 Web API, 在 WebForm 中提供 Web API, 通过 Web API 上传文件, .net 4.5 带来的更方便的异步操作
- 在ASP.NET MVC中实现一种不同于平常的三级联动、级联方式, 可用于城市、车型选择等多层级联场景
- 主攻ASP.NET.4.5.1 MVC5.0之重生:创建UIHelper通用自定义分页和选择开关与PagesHelper和IsSelect简单用法