ASP.NET MVC提醒我旧的经典ASP意大利面条代码 [英] ASP.NET MVC reminds me of old Classic ASP spaghetti code

问题描述

我刚刚通过一些MVC教程后检查了这个网站了一会儿。它只是我，或者MVC视图页面带来经典ASP意大利面条代码的所有跳入和跳出HTML和ASP.NET的黄色定界符无处不在使无法阅读的HORRIBLE闪回？什么发生了代码/设计分离的重要性？我真的卖的新技术，直到教程打开查看页面开发部分。

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.

还是我错过了什么？ （不要说你可以使用模板帮助，因为它是jsut移动意大利面到另一个位置 - 扫描它在地毯下 - 它不能解决这个问题）

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)

推荐答案

查看Jeff的信息（ http：// www.codinghorror.com/blog/archives/001155.html ），回应您的问题，以及Rob Conery的回应（ 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为开发者提供了在脚下拍摄自己的选择，虽然它可以干净地做。因此，它适合那些喜欢web开发和干净的风格的开发人员，但不是为那些想要Widgetized行为的开发人员而言，不必深入到标记中。

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意大利面条代码的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！