blocks|key|829128|text|我用火花。它在HTML和代码之间有很好的流。Scott还在帖子上发布了他每周一次的源代码评论文章。我真的很喜欢挖掘它。主要特性之一是视图的预编译。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|829129|entityMap|0|LINK|mutability|MUTABLE|url|http://dev.dejardin.org/|1|http://www.hanselman.com/blog/TheWeeklySourceCode30SparkAndNHamlCrazyASPNETMVCViewEngines.aspx|2|http://dev.dejardin.org/documentation/precompiling^0|2|2|0|T|2|1|1X|3|2|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]]]

I use <a href="http://dev.dejardin.org/" rel="nofollow noreferrer">Spark</a>. It has nice flow between HTML and code. Scott Hanselman also did a <a href="http://www.hanselman.com/blog/TheWeeklySourceCode30SparkAndNHamlCrazyASPNETMVCViewEngines.aspx" rel="nofollow noreferrer">post</a> on it with his weekly source code review posts. I am really digging it a lot. One of the major features is <a href="http://dev.dejardin.org/documentation/precompiling" rel="nofollow noreferrer">pre-compilation</a> of your views.

blocks|key|124514|text|NHaml是我最喜欢的，因为它简洁。人们要么喜欢它，要么讨厌它，因为它看起来与传统的“带有插入代码的HTML”模板系统非常不同，比如ASPX或NVelocity。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|124515|编辑：|offset|length|style|BOLD|124516|@Ben，|124517|还有其他的视图引擎可以编译下来(NHaml是其中之一)，所以这些引擎确实支持定制的helpers。看到当前解释的视图引擎最终最终得到编译模型，我不会感到惊讶。|124518|entityMap^0|0|0|3|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

NHaml is my favorite for its terseness. People either love it or hate it, given that it looks very different from a traditional "HTML with inserted code" template system like ASPX or NVelocity.

Edit:

@Ben,

There are other view engines which compile down (NHaml is one), so those do support custom HTML helpers. I wouldn't be surprised to see the currently interpreted view engines all eventually end up with a compilation model eventually.

blocks|key|124573|text|“StackOverflow使用哪种？”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|124574|网页表格。|124575|我问杰夫·阿特伍德关于他在“汤”标签上的决定。他没有回答--我想他正忙着找一个失踪的结束语;-)|124576|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|$]]

"Which does StackOverflow use?"

Web Forms.

I asked Jeff Atwood about his decision on his Tag Soup post. He didn't reply - I think he was busy hunting down a missing closing tag ;-)

blocks|key|1123894|text|微软最近宣布了一个新的视图引擎:剃须刀。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1123895|看起来很有趣：http://weblogs.asp.net/scottgu/archive/2010/07/02/introducing-razor.aspx|offset|length|1123896|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/scottgu/archive/2010/07/02/introducing-razor.aspx^0|0|7|20|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Microsoft has recently announced a new view engine: Razor.

Looks pretty interesting:
<a href="http://weblogs.asp.net/scottgu/archive/2010/07/02/introducing-razor.aspx" rel="nofollow noreferrer">http://weblogs.asp.net/scottgu/archive/2010/07/02/introducing-razor.aspx</a>

blocks|key|824960|text|地球上的大多数人只会使用ASPX，因为这是他们所知道的。另一个很好的好处是汇编的性质.因此，您不仅可以获得类型安全和智能感知，而且还可以获得额外的好处。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|824961|我看到的缺点是它太冗长了。我把一款应用程序转换成了NVelocity，它看上去是多么干净，这让我大吃一惊。问题是，有很多东西不适用于NVelocity+(比如您自己的自定义视图帮助程序)，而且严重缺乏文档。|824962|我在MvcContrib中添加了一个特性，您可以在其中注册自己的HtmlExtension类型，但在找到更好的解决方案之前，它更像是绷带。|824963|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|$]]

Most people on the planet will just use ASPX because that's what they know. Another excellent benefit is the compiled-nature... so you not only get type-safety and intellisense, but you can get the perf benefit as well.

The drawback that I see is that it's so flippin' verbose. I converted an app to NVelocity and was astounded at how clean it looked. The problem is that there were a lot of things that didn't work with NVelocity (like your own custom view helpers) and there was a severe lack of documentation.

I added a feature to MvcContrib where you can register your own HtmlExtension types to it, but it's more of a bandaid until a better solution comes out.

blocks|key|124612|text|我以前用过NVelocity。在大多数情况下，它使代码变得非常简洁和简单；但是，通常情况下，它只是几个ViewData变量，这些变量都是由XSLT文件预先填充的。所以我想我的视图引擎应该是XSLT+(这是一种爱/讨厌的东西--扩展方法使它非常有用)和NVelocity。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|124613|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've used NVelocity in the past. For the most part it makes the code really clean and simple to follow; however, it normally ends up just being a few ViewData variables which have been filled up by XSLT files before hand. So I guess really my View Engine would be both XSLT (which is a love/hate thing - Extension Methods make it really useful) and NVelocity.

blocks|key|829174|text|我在MonoRail中使用MonoRail已经有一段时间了，但最近又转向了火花，用于Asp.Net+MVC和MonoRail。语法对我来说似乎很自然，但我想这是意料之中的。;)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|829175|entityMap|0|LINK|mutability|MUTABLE|url|http://dev.dejardin.org/^0|11|2|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]]]]

I've used NVelocity with MonoRail for some time but have recently switched to <a href="http://dev.dejardin.org" rel="nofollow noreferrer">Spark</a> for both Asp.Net MVC and MonoRail. The syntax seems very natural to me, but I guess that's to be expected. ;)

I know you can use several different view engines with ASP.NET MVC:

<ul>
<li>ASPX, obviously</li>
<li>NVelocity</li>
<li>Brail</li>
<li>NHaml</li>
<li>et al...</li>
</ul>

The default ASPX view engine seems to make the most sense to me, coming from an ASP.NET WebForms background. 

But, I wanted to get an idea of the pros and cons of each and see what most people are using. 

Which does StackOverflow use?

What View Engine are you using with ASP.NET MVC?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我知道您可以使用ASP.NET MVC使用几种不同的视图引擎：显然，ASPXNVelocity辫状NHaml等等..。对于我来说，默认的ASPX视图引擎似乎最有意义，它来自ASP.NET WebForms背景。但是，我想弄清楚每个人的优缺点，看看大多数人都在使用什么。StackOverflow使用哪种？

问您在ASP.NET MVC中使用的是什么视图引擎？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问您在ASP.NET MVC中使用的是什么视图引擎？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问您在ASP.NET MVC中使用的是什么视图引擎？
EN