当我将xmlDocument()转储到标签中并使用它的xsl转换显示时，我认为这很整洁。

HttpContext。项作为请求级缓存工具

throw new HttpException(404, "Article not found");

这将被ASP捕获。NET，它将返回customErrors页面。在最近的.NET每日小贴士中了解了这一点

这似乎是一个巨大而模糊的问题…… 但我将在这里介绍Reflection，因为它允许我做一些非常强大的事情，如可插拔的DALs等。

这是最好的一个。把它加到你的网里。配置更快的编译。这是3.5SP1后通过这个QFE。

<compilation optimizeCompilations="true">

Quick summary: we are introducing a new optimizeCompilations switch in ASP.NET that can greatly improve the compilation speed in some scenarios. There are some catches, so read on for more details. This switch is currently available as a QFE for 3.5SP1, and will be part of VS 2010. The ASP.NET compilation system takes a very conservative approach which causes it to wipe out any previous work that it has done any time a ‘top level’ file changes. ‘Top level’ files include anything in bin and App_Code, as well as global.asax. While this works fine for small apps, it becomes nearly unusable for very large apps. E.g. a customer was running into a case where it was taking 10 minutes to refresh a page after making any change to a ‘bin’ assembly. To ease the pain, we added an ‘optimized’ compilation mode which takes a much less conservative approach to recompilation.

通过在这里:

应用程序变量可以与web应用程序一起使用，以便在整个应用程序中进行通信。它在全局中初始化。Asax文件，并在该web应用程序的页面上使用的所有用户独立于他们创建的会话。