人们发现哪些 ASP.NET MVC 视图引擎比默认引擎更好？
这个问题已经过去一年了，我想知道现在 - 人们发现哪些视图引擎非常好，为什么？
It's been a year since this question and I'd like to know now - what view engines are people finding very good and why?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我相信最活跃的是 Spark View Engine。它有很好的记录，包括有关某些主题的视频。我个人使用过 NHAML 视图引擎< /a> 对于一个项目，我喜欢它，但文档几乎不存在。我还认为 NHAML 在添加功能和修复错误方面并不是很活跃。
我计划在未来的项目中使用 Spark View Engine。
I believe the most active one is the Spark View Engine. It is very well documented including videos on certain topics. I have personally used the NHAML View Engine for a project and I liked it but the documentation is almost non-existent. I also think NHAML is not very active as far as adding features and fixing bugs.
I am planning on using the Spark View Engine in future projects.
如果您习惯 NVelocity 语法，NVelocity 视图引擎会很好。 MVC Contrib 项目已包含 MvcContrib.Castle.NVelocityViewFactory。
您可以从 www.codeplex.com/mvccontrib 下载
我从我正在学习的一本书中读到了这篇文章，但我希望它有所帮助，因为没有其他人回应。
NVelocity view engine is good if you're used to NVelocity syntax. The MVC Contrib project already contains MvcContrib.Castle.NVelocityViewFactory.
You can download from www.codeplex.com/mvccontrib
I read this out of a book I'm learining from, but I hope it helps since no one else responded.
我发现 NHAML 是朝着积极方向迈出的一步，并正在一个宠物项目中使用它来看看它的局限性。
Spark 可能有它的优点，但我不喜欢它基本上依赖于现有的语法。
这对我来说看起来很不舒服，但这只是个人的。
我担心的是新的视图引擎可能无法从 MVC2 中即将推出的助手中获益。
I find NHAML a move in the positive direction and am using it in a pet project to see what its limitations are.
Spark may have it advantages, but I dislike how it is basically piggy-backs on existing syntax.
It looks uncomfortable to me, but that's just personal.
What I'm worried about is that new view engines possibly won't be able to profit from the forthcoming helpers in MVC2.