blocks|key|411322|text|除非你正在工作的开发人员熟悉MVC模式，否则我不会，至少在做这么大的改变之前，我会先和他们谈谈。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|411323|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Unless the developers you are working with are familiar with MVC pattern I wouldn't. At a minimum I'd talk with them first before making such a big change.

blocks|key|3469339|text|我不建议仅仅在现有项目上进行转换。也许可以开始一个小的“演示”项目，团队可以使用它来试验技术，并(如果必要)了解他们需要什么，并向管理层证明进行转换是值得的。最后，即使是开发团队也可能会意识到他们还没有准备好，或者这不值得。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3469340|无论你做什么，一定要记录下来。如果你使用的是一个演示项目，也许可以写一篇文章供将来参考。|3469341|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 wouldn't recommend just making the switch on an existing project. Perhaps start a small "demo" project that the team can use to experiment with the technology and (if necessary) learn what they need to and demonstrate to management that it is worthwhile to make the switch. In the end, even the dev team might realize they aren't ready or it's not worth it.

Whatever you do, be sure to document it. Perhaps if you use a demo project, write a postmortem for future reference.

blocks|key|417107|text|我会先创建一个测试站点，然后看看团队的想法，但对我来说，在使用MVC之后，我不会再回到WebForms。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|417108|有些人不喜欢与HTML混合的代码，我可以理解，但我更喜欢灵活性，而不是像页面生命周期这样的东西，为我呈现HTML和biggy+-页面源代码中没有嵌入的视图状态。|417109|有些人更喜欢MVC以获得更好的可证性，但就我个人而言，我的大部分代码都在中间层，而且无论如何都很容易测试……|417110|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|$]]

I would create a test site first, and see what the team thinks, but for me I wouldn't go back to WebForms after using MVC.

Some people don't like code mixed with HTML, and I can understand that, but I far prefer the flexibility over things like Page Lifecycle, rendering HTML and biggy for me - no viewstate cruft embedded in the page source.

Some people prefer MVC for better testibility, but personally most of my code is in the middle layer and easily tested anyway...

blocks|key|3469350|text|我不知道MVC+MVC，但我非常熟悉ASP.NET模式。在没有MVC的情况下，我看不到其他构建专业应用程序的方法。而且它必须是MVC模型2，像Spring或Struts。顺便问一下，你们这些人是如何在没有MVC的情况下构建web应用程序的？当您遇到需要对每个请求进行某种类型验证的情况时，例如验证用户是否已通过身份验证，您的解决方案是什么？在每个页面中包含某种形式的(validate.aspx)？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3469351|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I dont´t know ASP.NET MVC, but I am very familiar with MVC pattern. I don´t see another way to build professional applications without MVC. And it has to be MVC model 2, like Spring or Struts. By the way, how you people were building web applications without MVC? When you have a situation that some kind of validation is necessary on every request, as validating if user is authenticated, what is your solution? Some kind of include(validate.aspx) in every page?

blocks|key|411331|text|我正在尝试对ASP.NET+MVC和Juan+Manuel做出同样的决定。我现在正在等待合适的小项目出现，我可以进行实验。如果实验进行得很顺利--我的直觉说它会成功--那么我将围绕这个框架设计我的新的大型项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|411332|使用Web，您将失去ASP.NET+ASP.NET窗体的视图状态/回发模型。如果没有这种抽象，您可以更紧密地使用HTML以及HTTP+POST和GET命令。我认为UI编程在某种程度上是在向经典的ASP方向发展。|411333|随之而来的是更大程度的控制。我经常发现自己在与ASP.NET的伪会话垃圾作斗争，重新获得对输出HTML的完全控制的前景似乎非常令人耳目一新。|411334|这可能是两个世界中最好的，也可能是最坏的。|411335|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/1782/juan-manuel^0|I|B|0|0|0|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|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

I'm trying to make that same decision about ASP.NET MVC, <a href="https://stackoverflow.com/users/1782/juan-manuel">Juan Manuel</a>. I'm now waiting for the right bite-sized project to come along with which I can experiment. If the experiment goes well--my gut says it will--then I'm going to architect my new large projects around the framework.

With ASP.NET MVC you lose the viewstate/postback model of ASP.NET Web Forms. Without that abstraction, you work much more closely with the HTML and the HTTP POST and GET commands. I believe the UI programming is somewhat in the direction of classic ASP.

With that inconvenience, comes a greater degree of control. I've very often found myself fighting the psuedo-session garbage of ASP.NET and the prospect of regaining complete control of the output HTML seems very refreshing.

It's perhaps either the best--or the worst--of both worlds.

blocks|key|417122|text|不，你不应该。你可以在一个新的项目中尝试它，但是很多熟悉HTML的人还不喜欢它，因为他们不得不处理原始的ASP.NET+%2B许多不同的概念%2B相当少的文档/教程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|417123|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

No, you shouldn't. Feel free to try it out on a new project, but a lot of people familiar with ASP.NET webforms aren't loving it yet, due to having to muck around with raw HTML + lots of different concepts + pretty slim pickings on documentation/tutorials.

blocks|key|411357|text|@Juan+Manuel你有没有在经典ASP中工作过？当你不得不编写你自己的所有事件和“视图统计”项时(就像一个下拉列表在表单提交后调用它的选定值)？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|411358|如果是这样的话，ASP.NET+MVC就不会感到尴尬了。我会看看Rob+Conery的Awesome+"MVC+Storefront“，他在那里浏览了框架，并为一个店面站点构建了每个预期的组件。它真的令人印象深刻，很容易跟进(追赶很难，因为Rob在那个系列中非常活跃，发布了很多帖子)。|offset|length|411359|就我个人而言，与Jeff+Atwood的feelings+on+the+topic截然相反，我更喜欢webform模型。这与vbscript/经典ASP时代完全不同，但实际上，让viewstate保持在可控状态并编写自己的CSS友好控件是一件令人愉快的事情。|411360|再说一次，注意我说的是“喜欢”。ASP.NET+MVC真的很棒，更像是其他的web技术。如果您喜欢或需要在多个平台上工作，从ASP.NET+MVC转换到RAILS当然更容易。虽然，是的，它显然是非常稳定的(就是这个网站)，如果你的公司不允许任何颜色的"beta“软件；在这个时候将其应用到生产中可能是一个问题。|411361|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.wekeroad.com/mvc-storefront/|1|https://stackoverflow.fogbugz.com/default.asp?W24212^0|0|1G|E|0|0|K|L|1|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

@Juan Manuel Did you ever work in classic ASP? When you had to program all of your own events and "viewstatish" items (like a dropdown recalling its selected value after form submission)?

If so, then ASP.NET MVC will not feel that awkward off the bat. I would check out Rob Conery's Awesome Series "<a href="http://blog.wekeroad.com/mvc-storefront/" rel="nofollow noreferrer">MVC Storefront</a>" where he has been walking through the framework and building each expected component for a storefront site. It's really impressive and easy to follow along (catching up is tough because Rob has been reall active and posted A LOT in that series).

Personally, and quite contrary to Jeff Atwood's <a href="https://stackoverflow.fogbugz.com/default.asp?W24212" rel="nofollow noreferrer">feelings on the topic</a>, I rather liked the webform model. It was totally different than the vbscript/classic ASP days for sure but keeping viewstate in check and writing your own CSS friendly controls was enjoyable, actually.

Then again, note that I said "liked". ASP.NET MVC is really awesome and more alike other web technologies out there. It certainly is easier to shift from ASP.NET MVC to RAILS if you like to or need to work on multiple platforms. And while, yes, it is very stable obviously (this very site), if your company disallows "beta" software of any color; implementing it into production at the this time might be an issue.

blocks|key|414884|text|在研究时，ASP.net+MVC只在“预览版5”中是一个值得关注的问题吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|414885|我知道StackOverflow是用它创建的，但微软有没有可能在它正式发布测试版/alpha版/预览版之前对框架进行重大修改？|414886|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|$]]

Is the fact that ASP.net MVC is only in 'Preview 5' be a cause for concern when looking into it? 

I know that StackOverflow was created using it, but is there a chance that Microsoft could implement significant changes to the framework before it is officially out of beta/alpha/preview release?

blocks|key|3256201|text|我不知道MVC+MVC，但我非常熟悉ASP.NET模式。在没有MVC的情况下，我看不到其他构建专业应用程序的方法。而且它必须是MVC模型2，像Spring或Struts。顺便问一下，你们这些人是如何在没有MVC的情况下构建web应用程序的？当您遇到需要对每个请求进行某种类型验证的情况时，例如验证用户是否已通过身份验证，您的解决方案是什么？在每个页面中包含某种形式的(validate.aspx)？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3256202|3256203|您是否从未听说过N-Tier开发？|3256204|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|H|8|@]|9|@]|A|$]]|$1|C|3|D|5|6|7|I|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|J|8|@]|9|@]|A|$]]]|F|$]]

<blockquote>
 I dont´t know ASP.NET MVC, but I am very familiar with MVC pattern. I don´t see another way to build professional applications without MVC. And it has to be MVC model 2, like Spring or Struts. By the way, how you people were building web applications without MVC? When you have a situation that some kind of validation is necessary on every request, as validating if user is authenticated, what is your solution? Some kind of include(validate.aspx) in every page?
</blockquote>

Have you never heard of N-Tier development?

blocks|key|414888|text|我使用过ASP.NET+MVC+(我甚至编写了一个HTTPModule，让你可以用web.config定义路由)，但我仍然对它心怀不满。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|414889|这似乎是组织和生产力上的一大倒退。也许对某些人来说不是，但我已经弄清楚了webforms，它们对我来说并不构成使它们可维护的挑战。|414890|我不赞同现在流行的“测试一切”的风尚。|414891|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|$]]

I have used ASP.NET MVC (I even wrote a HTTPModule that lets you define the routes in web.config), and I still get a bitter taste in my mouth about it.

It seems like a giant step backwards in organization and productivity. Maybe its not for some, but I've got webforms figured out, and they present no challenge to me as far as making them maintainable.

That, and I don't endorse the current "TEST EVERYTHING" fad...

blocks|key|414586|text|@Jonathan+Holland我看到你被投票否决了，但这是一个非常有效的观点。我已经阅读了一些关于intertubes的帖子，人们似乎混淆了ASP.NET、MVC、和MVC+。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|414587|MVC本身就是一种设计模式。如果你所寻找的都是“关注点分离”，那么你当然可以通过webforms来实现。就我个人而言，我是标准n层环境中的MVP+pattern的铁杆粉丝。|offset|length|style|BOLD|414588|如果你真的想在ASP.NET世界中完全控制你的标记，那么MVC框架就是为你准备的。|414589|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/magazine/cc188690.aspx^0|0|9|4|1X|B|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@$D|V|E|W|1|X]]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

@Jonathan Holland I saw that you were voted down, but that is a VERY VALID point. I have been reading some posts around the intertubes where people seem to be confusing ASP.NET MVC <a href="http://www.asp.net/mvc/" rel="noreferrer">the framework</a> and MVC <a href="http://en.wikipedia.org/wiki/Model-view-controller" rel="noreferrer">the pattern</a>.

MVC in of itself is a DESIGN PATTERN. If all you are looking for is a "separation of concerns" then you can certainly achieve that with webforms. Personally, I am a big fan of the <a href="http://msdn.microsoft.com/en-us/magazine/cc188690.aspx" rel="noreferrer">MVP pattern</a> in a standard n-tier environment.

If you really want TOTAL control of your mark-up in the ASP.NET world, then MVC the ramework is for you.

blocks|key|3256215|text|重要的是要记住，MVC和WebForms并不是相互竞争的，两者并不是一帆风顺的。它们只是不同的工具。大多数人似乎将MVC与WebForms视为“一个必须比另一个更好的锤子”。这是错误的。一个是锤子，另一个是螺丝刀。两者都用于将事物组合在一起的过程中，但有不同的优点和缺点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3256216|如果其中一个给你留下了一个不好的品味，你可能是想用螺丝刀敲钉子。某些问题在WebForms中很麻烦，而在MVC中则变得优雅和简单，反之亦然。|3256217|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|$]]

It's important to keep in mind that MVC and WebForms are not competing, and one is not better than the other. They are simply different tools. Most people seem to approach MVC vs WebForms as "one must be a better hammer than the other". That is wrong. One is a hammer, the other is a screwdriver. Both are used in the process of putting things together, but have different strengths and weaknesses.

If one left you with a bad taste, you were probably trying to use a screwdriver to pound a nail. Certain problems are cumbersome with WebForms that become elegant and simple with MVC, and vice-versa.

blocks|key|414893|text|ASP.NET+MVC基本上允许您将代码的不同部分的职责分开。这使您能够测试您的应用程序。你可以测试你的视图，路由等。由于现在没有ViewState或回发，它也确实提高了应用程序的速度。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|414894|但是，也有缺点。因为您没有使用WebForms，所以不能使用任何ASP.NET控件。这意味着如果您想要创建一个GridView，您将运行一个for循环并手动创建表。如果你想在ASP.NET中使用MVC向导，那么你必须自己创建。|414895|如果你对ASP.NET+webform感到厌烦，想要自己执行所有的事情，这是一个很好的框架。但您需要记住，您是否会从重新创建所有内容中受益？|414896|一般来说，我更喜欢Webforms框架，因为它有丰富的控件套件和自动管道。|414897|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

ASP.NET MVC basically allows you to separate the responsibility of different sections of the code. This enable you to test your application. You can test your Views, Routes etc. It also does speed up the application since now there is no ViewState or Postback. 

BUT, there are also disadvantages. Since, you are no using WebForms you cannot use any ASP.NET control. It means if you want to create a GridView you will be running a for loop and create the table manually. If you want to use the ASP.NET Wizard in MVC then you will have to create on your own. 

It is a nice framework if you are sick and tired of ASP.NET webform and want to perform everything on your own. But you need to keep in mind that would you benefit from creating all the stuff again or not? 

In general I prefer Webforms framework due to the rich suite of controls and the automatic plumbing.

blocks|key|3256219|text|如果您现在对WebForms很满意，那么ASP.NET+MVC可能不适合您。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3256220|我对WebForms感到失望已经有很长一段时间了。我绝对不是一个人。web上的智能客户端、有状态的抽象在复杂的场景中严重崩溃。我碰巧喜欢HTML、Javascript和CSS。WebForms试图对我隐瞒这件事。对于并不复杂的问题，它也有一些非常复杂的解决方案。Webforms本身也很难测试，虽然你可以使用MVP，但对于web环境来说，它不是一个很好的解决方案……(与MVC相比)。|3256221|MVC会在以下情况下向您提出上诉：-您想要更多地控制您的HTML+-想要像其他平台一样的无缝ajax体验-想要可测试性-想要有意义的URLs讨厌处理回发和视图状态问题|3256222|至于预览版5的框架，它相当稳定，设计大部分都在那里，升级并不困难。我在Preview+1上启动了一个应用程序，并在最新的预览版发布后的几个小时内进行了升级。|3256223|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

If you are quite happy with WebForms today, then maybe ASP.NET MVC isn't for you.

I have been frustrated with WebForms for a really long time. I'm definitely not alone here. The smart-client, stateful abstraction over the web breaks down severely in complex scenarios. I happen to love HTML, Javascript, and CSS. WebForms tries to hide that from me. It also has some really complex solutions to problems that are really not that complex. Webforms is also inherently difficult to test, and while you can use MVP, it's not a great solution for a web environment...(compared to MVC).

MVC will appeal to you if...
- you want more control over your HTML
- want a seamless ajax experience like every other platform has
- want testability through-and-through
- want meaningful URLs
- HATE dealing with postback &amp; viewstate issues

And as for the framework being Preview 5, it is quite stable, the design is mostly there, and upgrading is not difficult. I started an app on Preview 1 and have upgraded within a few hours of the newest preview being available.

blocks|key|3256235|text|如果您是一名专业的ASP.NET开发人员，并且有时间学习新的东西，我当然会建议您花一些时间尝试ASP.NET+MVC。它可能不是你所有问题的解决方案，有很多项目可能会从传统的webform实现中受益更多，但在尝试弄清楚MVC的同时，你肯定会学到很多东西，它可能会带来很多你可以应用到工作中的想法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3256236|在尝试开发一个MVC宠物项目时，我在阅读许多博客文章和视频教程时注意到一件好事，那就是它们大多数都遵循当前的最佳实践(TDD，IoC，依赖注入，以及较低程度的POCO)，加上大量的JQuery，使用户的体验更有趣，这些东西我可以应用到我目前的webform应用程序上，而且我以前没有如此深入地暴露过。|3256237|webforms的ASP.NET+MVC方式和webforms是如此的不同，它会让你震撼一下，这对于一个开发者来说是非常好的！|3256238|OTOH对于web开发的初学者来说，我认为MVC绝对是一个更好的开始，因为它提供了一个开箱即用的良好设计模式，并且更接近web真正的工作方式(毕竟HTML是无状态的)。在MVC上，你决定每一个在网络上来回移动的字节(至少当你不会在html+helpers上发疯的时候)。一旦这个人做到了这一点，他或她将更好地准备好转移到由ASP.NET+webforms和服务器控件提供的“人工”设施。|3256239|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

If you are a professional ASP.NET developer, and have some time to spare on learning new stuff, I would certainly recommend that you spend some time trying out ASP.NET MVC. It may not be the solution to all your problems, and there are lots of projects that may benefit more from a traditional webform implementation, but while trying to figure out MVC you will certainly learn a lot, and it might bring up lots of ideas that you can apply on your job.

One good thing that I noticed while going through many blog posts and video tutorials while trying to develop a MVC pet-project is that most of them follow the current best practices (TDD, IoC, Dependency Injection, and to a lower extent POCO), plus a lot of JQuery to make the experience more interesting for the user, and that is stuff that I can apply on my current webform apps, and that I wasn't exposed in such depth before.

The ASP.NET MVC way of doing things is so different from webforms that it will shake up a bit your mind, and that for a developer is very good! 

OTOH for a total beginner to web development I think MVC is definitely a better start because it offers a good design pattern out of the box and is closer to the way that the web really works (HTML is stateless, after all). On MVC you decide on every byte that goes back and forth on the wire (at least while you don't go crazy on html helpers). Once the guy gets that, he or she will be better equipped to move to the "artificial" facilities provided by ASP.NET webforms and server controls.

blocks|key|3256241|text|如果您决意使用MVC框架，那么我宁愿开始使用Castle项目的框架……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3256242|话虽如此，但我个人认为WebControls有很多优势，比如能够创建具有状态客户端的事件驱动的应用程序等等。大多数反对WebControls的论据都是因为缺乏对WebControl模型的理解而构建的，而不是因为它们实际上真的很糟糕……|3256243|MVC不是银弹，尤其不是Microsoft+MVC...|3256244|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|$]]

If you are dead set on using an MVC framework, then I would rather set out to use Castle project's one...

When that's said I personally think WebControls have a lot of advantages, like for instance being able to create event driven applications which have a stateful client and so on. Most of the arguments against WebControls are constructed because of lack of understanding the WebControl model etc. And not because they actually are truly bad...

MVC is not a Silver Bullet, especially not Microsoft MVC...

blocks|key|3256246|text|如果您喜欢使用为您做大量工作的服务器控件，您将不会喜欢MVC，因为您将需要在MVC中进行大量手工编码。如果你喜欢这个GridView，你可以自己写或者用别人的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3256247|MVC并不适合每个人，特别是如果您不喜欢对GUI部分进行单元测试。如果你对web表单感到满意，那就继续使用它。WebForms4.0将修复当前的一些缺点，比如ID是由ASP.NET自动分配的，您将在下一个版本中控制这些缺点。|3256248|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 like to use server controls which do a lot of work for you, you will NOT like MVC because you will need to do a lot of hand coding in MVC. If you like the GridView, expect to write one yourself or use someone else's.

MVC is not for everyone, specially if you're not into unit testing the GUI part. If you're comfortable with web forms, stay with it. Web Forms 4.0 will fix some of the current shortcomings like the ID's which are automatically assigned by ASP.NET. You will have control of these in the next version.

blocks|key|3256250|text|我见过一些MVC框架的实现，其中为了可测试性，有人在代码中呈现了整个HTML。在这种情况下，视图也是一个可测试的代码。但是我说，我的朋友，把HTML放在代码中是维护的噩梦，他说，我喜欢所有编译和测试的东西。我没有争论，但后来发现他确实把这个HTML放到了资源文件中，而且疯狂的还在继续……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3256251|他几乎没有意识到，分离视图的整个想法也解决了维护部分。在某些应用程序中，它比可测试性更重要。如果我们使用WYSWYG工具，我们不需要测试HTML设计。出于这个原因，WebForms是很好的。|3256252|我经常看到人们滥用回发和视图状态，并将其归咎于ASP+.NET模型。|3256253|记住，最好的网页仍然是.HTMLs，这就是ASP+.NET的强大之处。|3256254|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I have seen some implementation of MVC framework where for the sake of testability, someone rendered the whole HTML in code. In this case the view is also a testable code. But I said, my friend, putting HTML in code is a maintenance nightmare and he said well I like everything compiled and tested. I didn't argue, but later found that he did put this HTML into resource files and the craziness continued...

Little did he realized that the whole idea of separating View also solved the maintenance part. It outweighs the testability in some applications. We do not need to test the HTML design if we are using WYSWYG tool. WebForms are good for that reason.

I have often seen people abusing postback and viewstate and blaming it on the ASP .NET model. 

Remember the best webpages are still the .HTMLs and that's where is the Power of ASP .NET MVC.

blocks|key|3256256|text|5+Reasons+You+Should+Take+a+Closer+Look+at+ASP.NET+MVC|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3256257|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/dwahlin/archive/2009/04/06/5-reasons-you-should-take-a-closer-look-at-asp-net-mvc.aspx^0|0|1I|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<h2><a href="http://weblogs.asp.net/dwahlin/archive/2009/04/06/5-reasons-you-should-take-a-closer-look-at-asp-net-mvc.aspx" rel="nofollow noreferrer">5 Reasons You Should Take a Closer Look at ASP.NET MVC</a></h2>

blocks|key|414603|text|Ajax，RAD+(使用ajax的webforms通常是反RAD的)，完全控制(不需要开发一大堆代码和周期)。webforms只适用于绑定一些网格之类的东西，而不适用于其他任何东西，还有一件更重要的事情--性能。当你陷入web表单的地狱时，你迟早会切换到MVC。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|414604|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Ajax, RAD (webforms with ajax are anti-RAD very often), COMPLETE CONTROL (without developing whole bunch of code and cycles). webforms are good only to bind some grid and such and not for anything else, and one more really important thing - performance. when u get stuck into the web forms hell u will switch on MVC sooner or later.

I just listened to the StackOverflow team's 17th podcast, and they talked so highly of <a href="http://www.asp.net/mvc/" rel="noreferrer">ASP.NET MVC</a> that I decided to check it out.

But first, I want to be sure it's worth it. I already created a base web application (for other developers to build on) for a project that's starting in a few days and wanted to know, based on your experience, if I should take the time to learn the basics of MVC and re-create the base web application with this model.

Are there really big pros that'd make it worthwhile?

EDIT: It's not an existing project, it's a project about to start, so if I'm going to do it it should be now...

<hr>

I just found this

<blockquote>
 It does not, however, use the existing post-back model for interactions back to the server. Instead, you'll route all end-user interactions to a Controller class instead - which helps ensure clean separation of concerns and testability (it also means no viewstate or page lifecycle with MVC based views).
</blockquote>

How would that work? No viewstate? No events?

Should I migrate to ASP.NET MVC?

身份验证

单元测试

服务器

路由

我刚刚听了StackOverflow团队的第17期播客，他们对的评价非常高，我决定去看看。但首先，我想确定这是值得的。我已经为一个项目创建了一个基础web应用程序(供其他开发人员构建)，该项目将在几天后启动，根据您的经验，我想知道是否应该花时间学习MVC的基础知识，并使用此模型重新创建基础web应用程序。真的有很大的优...

问我应该迁移到ASP.NET MVC吗？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我应该迁移到ASP.NET MVC吗？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我应该迁移到ASP.NET MVC吗？
EN