9  

One of the goals of ASP.NET MVC is to give you control of your markup. However, there have always been choices with ASP.NET which would allow you to generate relatively clean HTML.

ASP.NET MVC的目标之一是让您控制标记。但是,ASP.NET一直有选择,允许您生成相对干净的HTML。

For instance, ASP.NET has always offered a choice with validator controls. Do you value development speed over markup? Use validators. Value markup over development speed? Pick another validation mechanism. Your comments on validators are kind of contradictory there - it's possible to use ASP.NET and still make choices for markup purity over development speed.

例如,ASP.NET总是提供验证器控件的选择。您是否重视开发速度而不是标记?使用验证器。价值加速超过发展速度?选择另一种验证机制。您对验证器的评论在那里是有点矛盾的 - 可以使用ASP.NET并且仍然可以选择标记纯度而不是开发速度。

Also, with webforms, we've had the CSS Friendly Control Adapters for a few years which will modify the controls to render more semantic markup. ASP.NET 3.5 included the ListView, which makes it really easy to write repeater type controls which emit semantic HTML. We used ASP.NET webforms on the Microsoft PDC site and have kept the HTML pretty clean: http://microsoftpdc.com/Agenda/Speakers.aspx - the Viewstate could probably be disabled on most pages, although in reality it's only a few dozen bytes.

此外,使用webforms,我们已经有了几年的CSS友好控制适配器,它将修改控件以呈现更多的语义标记。 ASP.NET 3.5包含了ListView,这使得编写发出语义HTML的转发器类型控件变得非常容易。我们在Microsoft PDC站点上使用了ASP.NET webforms并保持了HTML非常干净:http://microsoftpdc.com/Agenda/Speakers.aspx - Viewstate可能在大多数页面上被禁用,尽管实际上它只是少数几个十几个字节。

3  

You were on the right track. It is the fact that they are using the ASP.NET MVC web framework. It allows you to have full control of your output html.

你走在正确的轨道上。事实上,他们正在使用ASP.NET MVC Web框架。它允许您完全控制输出html。

3  

The ASP.NET MVC Framework is an alternative to the normal "web forms" way of doing ASP.NET development. With it you lose a lot of abstraction, but gain a lot of control.

ASP.NET MVC框架是执行ASP.NET开发的常规“Web表单”方式的替代方法。有了它你会失去很多抽象,但获得了很多控制权。

2  

Yes - MVC doesn't utilize the ASP.NET view state junk.

是的 - MVC不使用ASP.NET视图状态垃圾。