为什么要搬到Asp.NET MVC - 为什么不动 [英] Why to move to Asp.NET MVC - why not to move

查看:105
本文介绍了为什么要搬到Asp.NET MVC - 为什么不动的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

简单,因为它是:
为什么要搬到Asp.NET MVC和放大器;为什么不动(如果有任何理由)?

Simple as it is : Why to move to Asp.NET MVC & why not to move ( if there is any reason ) ?

添加

这是个必要动?
我们可以说,未来属于ASP.NET MVC?
多少年,你认为它可以停留在顶端?

Is it a necessity to move ? Can we say the future belongs to asp.net mvc ? How many years do you think it can stays on top ?

推荐答案

MVC得多构造良好,allowes为更好code分离和控制标记,并在服务器上要轻得多,那恕我直言唯一理由不动是,如果你有一个旧的.NET应用程序(或其他),它完美的工作,而你不希望在不久的将来就可以进行重大调整/修复。

MVC is much more well constructed, allowes for much better code seperation and control over markup, and is much lighter on the server, that IMHO the only reason not to move is if you have a legacy .NET application (or other) that is working flawlessly, and you're not expected to perform serious adjustments / fixes on it in the near future.

如果你决定搬家,你应该知道,你就可以重新使用很少的Web表单界面和用户控件,因为MVS建有一点不同。你类库可以重用,如果他们写得好。在任何情况下,在MVC中写入东西比的WebForms快得多,即使从头进行。

If you do decide to move, you should know that you'll be able to reuse very little of your webforms GUI and user controls, since MVS is built a bit differently. You class libraries you could reuse, if they're written well. In any case, writing stuff in MVC is much faster than in WebForms, even if done from scratch.

这篇关于为什么要搬到Asp.NET MVC - 为什么不动的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆