Asp.net MVC VS Asp.Net [英] Asp.net MVC VS Asp.Net

问题描述

许多公司正在考虑将其在Asp.net中制作的现有应用程序转换为asp.net MVC，并且还在考虑asp.net wrt的性能问题asp.net mvc，您认为使用asp.net制作的Web应用程序也可以从现在开始的1-2年内是市场的标准.

lot of companies are considering converting their existing applications made in Asp.net to asp.net MVC and also considering the performance issue with asp.net w.r.t asp.net mvc do u think an web application made in asp.net also can standard in market 1-2 years from now???

推荐答案

看到当前情况，似乎几乎所有.net项目都在朝着MVC迈进.毫无疑问，是否在MVC中创建了所有新项目.

Seeing the current scenario it seems that almost all .net projects are moving towards MVC. It would not wonder if there are all new projects being made in MVC.

asp.net永远不会消失..asp.net具有丰富的控件集，这些控件不适合asp. net MVC框架.无论首选多少asp.net mvc，asp.net Webform总是会存在

asp.net will never die.. asp.net has the rich set of controls which do not fit into asp.net MVC framework.. No matter how much asp.net mvc is preferred, asp.net webforms will always be there

个人而言，我更喜欢使用MVC框架.考虑到Web的移动方式，越来越多的移动\智能手机访问网站，UI变得越来越轻巧，带有用于客户端交互的javascript组件的HTML.

MVC模式更自然地适合于Web的无状态本质，并且框架的整体感觉与此相关.我一直觉得Web表单试图弥合``传统''VB6表单设计和Web之间的鸿沟，尽管这有助于从迁移到.Net框架的人们(很多年前！)中汲取学习经验，但是却确实起到了作用''不能真正代表网络.

在我工作的公司中，我们仍然有许多Webforms管理"应用程序已经存在了很多年.它们仍然可以工作，可以完成工作，在内部使用，因此我们不必考虑移动或跨浏览器的考虑-我认为不值得花很多时间在MVC中重新定义它们，因为我们可以这样做.

但是，对于所有的新开发，我们肯定会使用MVC. 严格地面向客户的任何事物都使用MVC，并具有基于主干或剔除的UI设计.借助MVC，我们可以与Team City保持出色的持续集成环境，在每次签入时都会运行单元测试和UI测试.它简单且有效.

Personally, I much prefer working with the MVC framework. Considering the way the web is moving, with more and more sites being accessed by mobile \ smartphones, UIs are becoming more lightweight HTML with javascript components for client side interactivity.

The MVC pattern fits more naturally into the stateless nature of the web, and the overall feel of the framework is geared towards this. I always felt that webforms tried to bridge the gap between ''traditional'' VB6 forms design and the web, which while was helpful in taking the learning curve out of people moving into the .Net framework (many years ago!) didn''t truly represent the web.

At the company I work for, we still have many Webforms ''administration'' applications that have been around for years. They still work, they do their job, they are internally used so we don''t have to consider mobile or cross browser considerations - in my opinion it''s not worth the man hours to redeisgn them in MVC just because we can.

However, for all new developments, we''re definitely using MVC. Anything customer facing is strictly using MVC, with backbone or knockout based UI designs. With MVC we get a brilliant continuous intergration environment with Team City, with unit tests and UI tests run as part of every check in. It''s simple and it works.

这篇关于Asp.net MVC VS Asp.Net的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！