ASP.NET MVC让我想起了老经典ASP意大利面条code的 [英] ASP.NET MVC reminds me of old Classic ASP spaghetti code

问题描述

我只是通过一些MVC教程去检查这个网站了一会儿之后。难道只是我，还是MVC View页面带回经典ASP意大利面条code的太可怕了倒叙与和所有跳跃的HTML和ASP.NET与黄色的分隔符随处使其无法读取？什么都发生在code /设计分离的重要性？我真的对新技术出售，直到教程命中查看页面开发部分。

I just went through some MVC tutorials after checking this site out for a while. Is it just me, or does MVC View pages bring back HORRIBLE flashbacks of Classic ASP spaghetti code with all the jumping in and out of HTML and ASP.NET with yellow delimiters everywhere making it impossible to read? What ever happened to the importance of code/design separation?? I was really sold on the new technology until the tutorials hit the View page development section.

还是我失去了一些东西？ （不要说你可以使用模板来帮助，因为它是仅仅指刚动面条到另一个位置 - 在地毯下扫它 - 它不解决问题）

Or am I missing something? (And don't say you can use the template to help because it's jsut moving the spaghetti to another location - sweeps it under the rug - it doesn't fix the problem)

推荐答案

看到杰夫的职位（<一个href=\"http://www.codinghorror.com/blog/archives/001155.html\">http://www.codinghorror.com/blog/archives/001155.html)呼应你的问题，并罗布科纳的响应（<一个href=\"http://blog.wekeroad.com/blog/asp-net-mvc-avoiding-tag-soup/\">http://blog.wekeroad.com/blog/asp-net-mvc-avoiding-tag-soup/)

see Jeff's post (http://www.codinghorror.com/blog/archives/001155.html) which echoes your question, and Rob Conery's response (http://blog.wekeroad.com/blog/asp-net-mvc-avoiding-tag-soup/)

总之，ASP.NET MVC使开发人员在脚下拍摄自己的选择，虽然它当然可以干净地做到这一点。因此，它适合于开发谁是舒适与网络开发和拥有清新的风格，但它不是谁想要部件化的行为，一拉的WinForms，而不必太深入钻研这些标记的开发者。

In summary, ASP.NET MVC gives developers the choice of shooting themselves in the foot, although it's certainly possible to do it cleanly. As such, it is suited for developers who are comfortable with web development and have a clean style, but it is not for the developers who want Widgetized behavior a la winforms without having to delve too deeply into the markup.

这篇关于ASP.NET MVC让我想起了老经典ASP意大利面条code的的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！