blocks|key|1136150|text|在测试时，可以将电子邮件发送到计算机上的文件夹，而不是SMTP服务器。把这个放在你的web.config中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1136151|<system.net>
++++<mailSettings>
++++++++<smtp+deliveryMethod="SpecifiedPickupDirectory">
++++++++++++<specifiedPickupDirectory+pickupDirectoryLocation="c:\Temp\"+/>
++++++++</smtp>
++++</mailSettings>
</system.net>|code-block|syntax|javascript|1136152|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

While testing, you can have emails sent to a folder on your computer instead of an SMTP server. Put this in your web.config:

<pre><code>&lt;system.net&gt;
 &lt;mailSettings&gt;
 &lt;smtp deliveryMethod="SpecifiedPickupDirectory"&gt;
 &lt;specifiedPickupDirectory pickupDirectoryLocation="c:\Temp\" /&gt;
 &lt;/smtp&gt;
 &lt;/mailSettings&gt;
&lt;/system.net&gt;
</code></pre>

blocks|key|1136018|text|如果将名为app_offline.htm的文件放置在web应用程序目录的根目录中，ASP.NET+2.0%2B将关闭应用程序并停止正常处理该应用程序的任何新传入请求，只显示所有新请求的app_offline.htm文件内容。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1136019|这是在将更改重新部署(或回滚)到生产服务器时显示“站点暂时不可用”通知的最快捷和最简单的方法。|1136020|另外，正如马克斯所指出的，确保文件中至少有512个字节的内容，以便IE6能够正确地呈现它。|1136021|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/1659/marxidad^0|5|F|0|0|5|3|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|V|8|@]|D|@$9|W|A|X|1|Y]]|E|$]]|$1|J|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

If you place a file named app_offline.htm
in the root of a web application directory, ASP.NET 2.0+ will shut-down the application and stop normal processing any new incoming requests for that application, showing only the contents of the app_offline.htm file for all new requests.

This is the quickest and easiest way to display your "Site Temporarily Unavailable" notice while re-deploying (or rolling back) changes to a Production server.

Also, as pointed out by <a href="https://stackoverflow.com/users/1659/marxidad">marxidad</a>, make sure you have at least 512 bytes of content within the file so IE6 will render it correctly.

blocks|key|137077|text|throw+new+HttpException(404,+"Article+not+found");|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|137078|这将被ASP.NET捕获，它将返回customErrors页面。在最近的.NET贴士日邮报中了解到了这个|unstyled|offset|length|137079|entityMap|0|LINK|mutability|MUTABLE|url|http://dotnettipoftheday.org/tips/how-to-respond-with-code-404-not-found-in-aspnet.aspx?discussion=1^0|0|X|C|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|R|8|@]|9|@$G|S|H|T|1|U]]|A|$]]|$1|I|3|-4|5|F|7|V|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

<pre><code>throw new HttpException(404, "Article not found");
</code></pre>

This will be caught by ASP.NET which will return the customErrors page. Learned about this one in a <a href="http://dotnettipoftheday.org/tips/how-to-respond-with-code-404-not-found-in-aspnet.aspx?discussion=1" rel="nofollow noreferrer">recent .NET Tip of the Day Post</a>

blocks|key|137794|text|这是最好的。将其添加到web.config以获得更快的编译速度。这是post+3.5SP1通过本QFE。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|137795|<compilation+optimizeCompilations="true">|code-block|syntax|javascript|137796|快速总结:我们在ASP.NET中引入了一个新的ASP.NET开关，它可以大大提高某些情况下的编译速度。有一些捕捉，所以阅读更多的细节。此开关目前可作为QFE的3.5SP1，并将是VS+2010的一部分。
ASP.NET编译系统采用了一种非常保守的方法，这使得它在任何时候“顶级”文件更改时都会删除以前所做的任何工作。“顶级”文件包括bin和App_Code中的任何内容，以及global.asax。虽然这在小型应用程序中很好，但对于非常大的应用程序却几乎无法使用。例如，客户在对“bin”程序集进行任何更改后，会遇到这样的情况:刷新页面需要10分钟。
为了减轻痛苦，我们增加了一种“优化”编译模式，这需要一种不太保守的方法来重新编译。|blockquote|137797|通过这里|137798|entityMap|0|LINK|mutability|MUTABLE|url|http://support.microsoft.com/kb/961884|1|http://blogs.msdn.com/davidebb/archive/2009/04/15/a-new-flag-to-optimize-asp-net-compilation-behavior.aspx^0|1B|4|0|0|0|0|2|2|1|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|F|7|11|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|K|7|12|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|N|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|W]]]]

Here's the best one. Add this to your web.config for MUCH faster compilation. This is post 3.5SP1 via <a href="http://support.microsoft.com/kb/961884" rel="nofollow noreferrer">this QFE</a>.

<pre><code>&lt;compilation optimizeCompilations="true"&gt;
</code></pre>

<blockquote>
 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.
</blockquote>

Via <a href="http://blogs.msdn.com/davidebb/archive/2009/04/15/a-new-flag-to-optimize-asp-net-compilation-behavior.aspx" rel="nofollow noreferrer">here</a>:

blocks|key|834844|text|HttpContext.Current总是允许您访问当前上下文的请求/响应/等，即使您无法访问页面的属性(例如，从松散耦合的助手类)。|type|unordered-list-item|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|834845|在将用户重定向到另一个页面后，可以通过调用Response.Redirect(url，+false+)继续在同一页上执行代码|834846|如果只需要编译的IHttpHandler).页面(或任何)，则不需要文件只需设置路径和HTTP方法，以指向web.config文件中的web.config中的类。|834847|可以通过调用PageParser.GetCompiledPageInstance(virtualPath，(上下文)从.ASPX文件中以编程方式检索.ASPX页面对象|834848|unstyled|entityMap^0|0|J|0|L|M|1E|1|0|8|C|S|1H|0|0|2B|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|M|7|14|8|@]|D|@]|E|$]]]|N|$]]

<ul>
<li>HttpContext.Current will always give you access to the current context's Request/Response/etc., even when you don't have access to the Page's properties (e.g., from a loosely-coupled helper class).</li>
<li>You can continue executing code on the same page after redirecting the user to another one by calling Response.Redirect(url, false )</li>
<li>You don't need .ASPX files if all you want is a compiled Page (or any IHttpHandler). Just set the path and HTTP methods to point to the class in the <a href="http://msdn.microsoft.com/en-us/library/aa903367%28VS.71%29.aspx" rel="nofollow noreferrer"><code>&lt;httpHandlers&gt;</code> element</a> in the web.config file.</li>
<li>A Page object can be retrieved from an .ASPX file programmatically by calling PageParser.GetCompiledPageInstance(virtualPath,aspxFileName,Context)</li>
</ul>

blocks|key|137643|text|machine.config级别的零售模式：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|137644|<configuration>
++<system.web>
++++<deployment+retail="true"/>
++</system.web>
</configuration>|code-block|syntax|javascript|137645|重写web.config设置以强制调试为false，打开自定义错误并禁用跟踪。不要忘记在发布之前更改属性--只需将它们全部配置为开发或测试环境，并更新生产零售设置。|137646|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Retail mode at the machine.config level: 

<pre><code>&lt;configuration&gt;
 &lt;system.web&gt;
 &lt;deployment retail="true"/&gt;
 &lt;/system.web&gt;
&lt;/configuration&gt;
</code></pre>

Overrides the web.config settings to enforce debug to false, turns custom errors on and disables tracing. No more forgetting to change attributes before publishing - just leave them all configured for development or test environments and update the production retail setting.

blocks|key|831374|text|在内容页中为MasterPages启用MasterPages智能感知|type|unstyled|depth|inlineStyleRanges|entityRanges|data|831375|我相信这是一个鲜为人知的黑客。|831376|在大多数情况下，您必须使用findcontrol方法并在母版页中从您想要使用的内容页中强制转换控件，MasterType指令将在您达到此目的后在visual+studio中启用intellisense。|offset|length|style|BOLD|831377|只需向页面再添加一个指令即可。|831378|<%25@+MasterType+VirtualPath="~/Masters/MyMainMasterPage.master"+%25>|code-block|syntax|javascript|831379|如果您不想使用虚拟路径，而是使用类名|831380|<%25@+MasterType+TypeName="MyMainMasterPage"+%25>|831381|获取完整的文章这里|831382|entityMap|0|LINK|mutability|MUTABLE|url|http://www.simple-talk.com/content/print.aspx?article=398^0|0|0|1E|A|0|0|0|0|0|7|2|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|16|8|@$F|17|G|18|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1A|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|N|7|1C|8|@]|9|@]|A|$O|P]]|$1|U|3|V|5|6|7|1D|8|@]|9|@$F|1E|G|1F|1|1G]]|A|$]]|$1|W|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

Enabling intellisense for MasterPages in the content pages 
I am sure this is a very little known hack

Most of the time you have to use the findcontrol method and cast the controls in master page from the content pages when you want to use them, the MasterType directive will enable intellisense in visual studio once you to this

just add one more directive to the page

<pre><code>&lt;%@ MasterType VirtualPath="~/Masters/MyMainMasterPage.master" %&gt;
</code></pre>

If you do not want to use the Virtual Path and use the class name instead then 

<pre><code>&lt;%@ MasterType TypeName="MyMainMasterPage" %&gt;
</code></pre>

Get the full article <a href="http://www.simple-talk.com/content/print.aspx?article=398" rel="nofollow noreferrer">here</a>

blocks|key|1135839|text|HttpContext.Items作为请求级缓存工具。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1135840|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|$]]

HttpContext.Items as a request-level caching tool

blocks|key|834824|text|有两件事在我的脑海中脱颖而出：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|834825|1)您可以从代码中打开或关闭跟踪：|834826|#ifdef+DEBUG+
+++if+(Context.Request.QueryString["DoTrace"]+==+"true")
++++++++++++++++{
++++++++++++++++++++Trace.IsEnabled+=+true;
++++++++++++++++++++Trace.Write("Application:TraceStarted");
++++++++++++++++}
#endif|code-block|syntax|javascript|834827|2)您可以只使用一个共享的“代码隐藏”文件构建多个.aspx页面。|834828|构建一个类.cs文件：|834829|public+class+Class1:System.Web.UI.Page
++++{
++++++++public+TextBox+tbLogin;

++++++++protected+void+Page_Load(object+sender,+EventArgs+e)
++++++++{

++++++++++if+(tbLogin!=null)
++++++++++++tbLogin.Text+=+"Hello+World";
++++++++}
++++}|834830|然后可以有任意数量的.aspx页面(在删除.designer.cs和.cs代码之后--+VS生成的代码后面)：|834831|++<%25@+Page+Language="C#"++AutoEventWireup="true"++Inherits="Namespace.Class1"+%25>
+++++<form+id="form1"+runat="server">
+++++<div>
+++++<asp:TextBox++ID="tbLogin"+runat="server"></asp:+TextBox++>
+++++</div>
+++++</form>|834832|您可以在ASPX中拥有不出现在Class1中的控件，反之亦然，但是您需要记住检查控件是否为空。|834833|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|11|8|@]|9|@]|A|$G|H]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|13|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

Two things stand out in my head:

1) You can turn Trace on and off from the code:

<pre><code>#ifdef DEBUG 
 if (Context.Request.QueryString["DoTrace"] == "true")
 {
 Trace.IsEnabled = true;
 Trace.Write("Application:TraceStarted");
 }
#endif
</code></pre>

2) You can build multiple .aspx pages using only one shared "code-behind" file.

Build one class .cs file :

<pre><code>public class Class1:System.Web.UI.Page
 {
 public TextBox tbLogin;

 protected void Page_Load(object sender, EventArgs e)
 {

 if (tbLogin!=null)
 tbLogin.Text = "Hello World";
 }
 }
</code></pre>

and then you can have any number of .aspx pages (after you delete .designer.cs and .cs code-behind that VS has generated) : 

<pre><code> &lt;%@ Page Language="C#" AutoEventWireup="true" Inherits="Namespace.Class1" %&gt;
 &lt;form id="form1" runat="server"&gt;
 &lt;div&gt;
 &lt;asp:TextBox ID="tbLogin" runat="server"&gt;&lt;/asp: TextBox &gt;
 &lt;/div&gt;
 &lt;/form&gt;
</code></pre>

You can have controls in the ASPX that do not appear in Class1, and vice-versa, but you need to remeber to check your controls for nulls.

blocks|key|137041|text|您可以使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|137042|+Request.Params[Control.UniqueId]+|code-block|syntax|javascript|137043|若要在初始化viewstate之前获取控件的值(此时Control.Text等将为空)。|137044|这对于Init中的代码很有用。|137045|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You can use:

<pre><code> Request.Params[Control.UniqueId] 
</code></pre>

To get the value of a control BEFORE viewstate is initialized (Control.Text etc will be empty at this point).

This is useful for code in Init.

blocks|key|137829|text|WebMethods.|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|137830|您可以对放在ASPX页面中的ASP.NET方法使用web回调。您可以用WebMethod()和ScriptMethod()属性来修饰静态方法。例如：|137831|[System.Web.Services.WebMethod()]+
[System.Web.Script.Services.ScriptMethod()]+
public+static+List<string>+GetFruitBeginingWith(string+letter)
{
++++List<string>+products+=+new+List<string>()+
++++{+
++++++++"Apple",+"Banana",+"Blackberry",+"Blueberries",+"Orange",+"Mango",+"Melon",+"Peach"
++++};

++++return+products.Where(p+=>+p.StartsWith(letter)).ToList();
}|code-block|syntax|javascript|137832|现在，在您的ASPX页面中，您可以这样做：|137833|<form+id="form1"+runat="server">
++++<div>
++++++++<asp:ScriptManager+ID="ScriptManager1"+runat="server"+EnablePageMethods="true"+/>
++++++++<input+type="button"+value="Get+Fruit"+onclick="GetFruit('B')"+/>
++++</div>
</form>|137834|并使用以下方法通过JavaScript调用服务器端方法：|137835|++++<script+type="text/javascript">
++++function+GetFruit(l)
++++{
++++++++PageMethods.GetFruitBeginingWith(l,+OnGetFruitComplete);
++++}

++++function+OnGetFruitComplete(result)
++++{
++++++++alert("You+got+fruit:+"+%2B+result);
++++}
</script>|137836|entityMap^0|0|B|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|13|8|@]|D|@]|E|$]]|$1|S|3|T|5|J|7|14|8|@]|D|@]|E|$K|L]]|$1|U|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|V|$]]

WebMethods.

You can using ASP.NET AJAX callbacks to web methods placed in ASPX pages. You can decorate a static method with the [WebMethod()] and [ScriptMethod()] attributes. For example:

<pre><code>[System.Web.Services.WebMethod()] 
[System.Web.Script.Services.ScriptMethod()] 
public static List&lt;string&gt; GetFruitBeginingWith(string letter)
{
 List&lt;string&gt; products = new List&lt;string&gt;() 
 { 
 "Apple", "Banana", "Blackberry", "Blueberries", "Orange", "Mango", "Melon", "Peach"
 };

 return products.Where(p =&gt; p.StartsWith(letter)).ToList();
}
</code></pre>

Now, in your ASPX page you can do this:

<pre><code>&lt;form id="form1" runat="server"&gt;
 &lt;div&gt;
 &lt;asp:ScriptManager ID="ScriptManager1" runat="server" EnablePageMethods="true" /&gt;
 &lt;input type="button" value="Get Fruit" onclick="GetFruit('B')" /&gt;
 &lt;/div&gt;
&lt;/form&gt;
</code></pre>

And call your server side method via JavaScript using:

<pre><code> &lt;script type="text/javascript"&gt;
 function GetFruit(l)
 {
 PageMethods.GetFruitBeginingWith(l, OnGetFruitComplete);
 }

 function OnGetFruitComplete(result)
 {
 alert("You got fruit: " + result);
 }
&lt;/script&gt;
</code></pre>

blocks|key|1136863|text|在启动长期运行的任务之前，检查客户端是否仍然连接：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1136864|if+(this.Response.IsClientConnected)
{
++//+long-running+task
}|code-block|syntax|javascript|1136865|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Check to see if the client is still connected, before starting a long-running task:

<pre><code>if (this.Response.IsClientConnected)
{
 // long-running task
}
</code></pre>

blocks|key|1136745|text|ASP.NET的一个鲜为人知且很少使用的特性是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1136746|标记映射|offset|length|1136747|它很少使用，因为只有特定的情况下你会需要它，但当你需要它，它是如此方便。|1136748|一些关于这个鲜为人知的特性的文章：|1136749|ASP.NET中的标记映射|1136750|在ASP.NET+2.0中使用标记映射|1136751|从最后一篇文章来看：|1136752|标记映射允许您在web应用程序中的每个页面上的编译时交换兼容的控件。一个有用的示例是，如果您有一个股票ASP.NET控件(如DropDownList+)，并且希望用从DropDownList派生的自定义控件替换它。这可能是一个已自定义以提供更优化的查找数据缓存的控件。与其编辑每个web表单并用自定义版本替换内置的DropDownLists，您还可以通过修改web.config来使ASP.NET实际上为您完成此操作：|blockquote|1136753|<pages>
+<tagMapping>
+++<clear+/>
+++<add+tagType="System.Web.UI.WebControls.DropDownList"
++++++++mappedTagType="SmartDropDown"/>
++</tagMapping>
</pages>|code-block|syntax|javascript|1136754|entityMap|0|LINK|mutability|MUTABLE|url|http://madskristensen.net/post/Tag-mapping-in-ASPNET.aspx|1|2|http://www.fmsinc.com/free/NewTips/NET/tag_mapping.html^0|0|0|4|0|0|0|0|0|D|1|0|0|J|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@$D|1A|E|1B|1|1C]]|A|$]]|$1|F|3|G|5|6|7|1D|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1E|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1F|8|@]|9|@$D|1G|E|1H|1|1I]]|A|$]]|$1|L|3|M|5|6|7|1J|8|@]|9|@$D|1K|E|1L|1|1M]]|A|$]]|$1|N|3|O|5|6|7|1N|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1O|8|@]|9|@]|A|$]]|$1|S|3|T|5|U|7|1P|8|@]|9|@]|A|$V|W]]|$1|X|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14]]|15|$5|10|11|12|A|$13|14]]|16|$5|10|11|12|A|$13|17]]]]

One little known and rarely used feature of ASP.NET is:

<a href="http://madskristensen.net/post/Tag-mapping-in-ASPNET.aspx" rel="nofollow noreferrer">Tag Mapping</a>

It's rarely used because there's only a specific situation where you'd need it, but when you need it, it's so handy.

Some articles about this little know feature:

<a href="http://madskristensen.net/post/Tag-mapping-in-ASPNET.aspx" rel="nofollow noreferrer">Tag Mapping in ASP.NET</a> 
<a href="http://www.fmsinc.com/free/NewTips/NET/tag_mapping.html" rel="nofollow noreferrer">Using Tag Mapping in ASP.NET 2.0</a>

and from that last article:

<blockquote>
 Tag mapping allows you to swap
 compatible controls at compile time on
 every page in your web application. A
 useful example is if you have a stock
 ASP.NET control, such as a
 DropDownList, and you want to replace
 it with a customized control that is
 derived from DropDownList. This could
 be a control that has been customized
 to provide more optimized caching of
 lookup data. Instead of editing every
 web form and replacing the built in
 DropDownLists with your custom
 version, you can have ASP.NET in
 effect do it for you by modifying
 web.config:
</blockquote>

<pre><code>&lt;pages&gt;
 &lt;tagMapping&gt;
 &lt;clear /&gt;
 &lt;add tagType="System.Web.UI.WebControls.DropDownList"
 mappedTagType="SmartDropDown"/&gt;
 &lt;/tagMapping&gt;
&lt;/pages&gt;
</code></pre>

blocks|key|136979|text|HttpModules。建筑非常优雅。也许不是隐藏的特征，但还是很酷。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|136980|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms227673.aspx^0|0|B|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]]]]

<a href="http://msdn.microsoft.com/en-us/library/ms227673.aspx" rel="nofollow noreferrer">HttpModules</a>. The architecture is crazy elegant. Maybe not a hidden feature, but cool none the less.

blocks|key|137433|text|您可以在ASP.NET页面中使用.aspx注释来注释页面的全部部分，包括服务器控件。而被注释掉的内容将永远不会发送给客户端。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|137434|<%25--
++++<div>
++++++++<asp:Button+runat="server"+id="btnOne"/>
++++</div>
--%25>|code-block|syntax|javascript|137435|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can use ASP.NET Comments within an .aspx page to comment out full parts of a page including server controls. And the contents that is commented out will never be sent to the client.

<pre><code>&lt;%--
 &lt;div&gt;
 &lt;asp:Button runat="server" id="btnOne"/&gt;
 &lt;/div&gt;
--%&gt;
</code></pre>

blocks|key|137613|text|代码表达式生成器|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|137614|样本标记：|137615|Text+=+'<%25$+Code:+GetText()+%25>'
Text+=+'<%25$+Code:+MyStaticClass.MyStaticProperty+%25>'
Text+=+'<%25$+Code:+DateTime.Now.ToShortDateString()+%25>'
MaxLenth+=+'<%25$+Code:+30+%2B+40+%25>'|code-block|syntax|javascript|137616|代码表达式生成器的真正优点是，您可以在非绑定情况下使用类似于表达式的绑定。您还可以创建执行其他功能的其他表达式生成器。|137617|web.config：|137618|<system.web>++++
++++<compilation+debug="true">
++++++++<expressionBuilders>
++++++++++++<add+expressionPrefix="Code"+type="CodeExpressionBuilder"+/>|137619|使这一切发生的cs类：|137620|[ExpressionPrefix("Code")]
public+class+CodeExpressionBuilder+:+ExpressionBuilder
{
++++public+override+CodeExpression+GetCodeExpression(
++++++++BoundPropertyEntry+entry,
++++++++object+parsedData,
++++++++ExpressionBuilderContext+context)
++++{++++++++++++
++++++++return+new+CodeSnippetExpression(entry.Expression);
++++}
}+|137621|entityMap^0|0|8|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|14|8|@]|D|@]|E|$]]|$1|Q|3|R|5|J|7|15|8|@]|D|@]|E|$K|L]]|$1|S|3|T|5|6|7|16|8|@]|D|@]|E|$]]|$1|U|3|V|5|J|7|17|8|@]|D|@]|E|$K|L]]|$1|W|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|X|$]]

The Code Expression Builder 

Sample markup:

<pre><code>Text = '&lt;%$ Code: GetText() %&gt;'
Text = '&lt;%$ Code: MyStaticClass.MyStaticProperty %&gt;'
Text = '&lt;%$ Code: DateTime.Now.ToShortDateString() %&gt;'
MaxLenth = '&lt;%$ Code: 30 + 40 %&gt;'
</code></pre>

The real beauty of the code expression builder is that you can use databinding like expressions in non-databinding situations. You can also create other Expression Builders that perform other functions.

web.config:

<pre><code>&lt;system.web&gt; 
 &lt;compilation debug="true"&gt;
 &lt;expressionBuilders&gt;
 &lt;add expressionPrefix="Code" type="CodeExpressionBuilder" /&gt;
</code></pre>

The cs class that makes it all happen:

<pre><code>[ExpressionPrefix("Code")]
public class CodeExpressionBuilder : ExpressionBuilder
{
 public override CodeExpression GetCodeExpression(
 BoundPropertyEntry entry,
 object parsedData,
 ExpressionBuilderContext context)
 { 
 return new CodeSnippetExpression(entry.Expression);
 }
} 
</code></pre>

blocks|key|137527|text|ASHX文件类型的使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|137528|如果您只想输出一些基本的html或xml，而不需要遍历页面事件处理程序，那么您可以以简单的方式实现HttpModule。|137529|将页面命名为SomeHandlerPage.ashx，只需将以下代码(仅一行)放入其中|137530|<%25@+webhandler+language="C#"+class="MyNamespace.MyHandler"+%25>|code-block|syntax|javascript|137531|然后，代码文件|137532|using+System;
using+System.IO;
using+System.Web;

namespace+MyNamespace
{
++++public+class+MyHandler:+IHttpHandler
++++{
++++++++public+void+ProcessRequest+(HttpContext+context)
++++++++{+++
++++++++++++context.Response.ContentType+=+"text/xml";
++++++++++++string+myString+=+SomeLibrary.SomeClass.SomeMethod();
++++++++++++context.Response.Write(myString);
++++++++}

++++++++public+bool+IsReusable
++++++++{
++++++++++++get+{+return+true;+}
++++++++}
++++}
}|137533|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Usage of the ASHX file type: 
If you want to just output some basic html or xml without going through the page event handlers then you can implement the HttpModule in a simple fashion

Name the page as SomeHandlerPage.ashx and just put the below code (just one line) in it

<pre><code>&lt;%@ webhandler language="C#" class="MyNamespace.MyHandler" %&gt;
</code></pre>

Then the code file

<pre><code>using System;
using System.IO;
using System.Web;

namespace MyNamespace
{
 public class MyHandler: IHttpHandler
 {
 public void ProcessRequest (HttpContext context)
 { 
 context.Response.ContentType = "text/xml";
 string myString = SomeLibrary.SomeClass.SomeMethod();
 context.Response.Write(myString);
 }

 public bool IsReusable
 {
 get { return true; }
 }
 }
}
</code></pre>

blocks|key|831197|text|基于目标浏览器的服务器控件属性设置和更多.|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|831198|”|blockquote|831199|那个让我大吃一惊。|831200|entityMap|0|LINK|mutability|MUTABLE|url|http://ryanfarley.com/blog/archive/2008/08/14/set-browser-specific-asp.net-server-control-properties-and-taking-an.aspx|1|http://ryanfarley.com/blog/archive/2008/08/14/more-on-device-filtering-with-asp.net-server-control-properties.aspx^0|0|H|0|I|2|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@]|C|$]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]|Q|$5|L|M|N|C|$O|R]]]]

<a href="http://ryanfarley.com/blog/archive/2008/08/14/set-browser-specific-asp.net-server-control-properties-and-taking-an.aspx" rel="nofollow noreferrer">Setting Server Control Properties Based on Target Browser</a> and <a href="http://ryanfarley.com/blog/archive/2008/08/14/more-on-device-filtering-with-asp.net-server-control-properties.aspx" rel="nofollow noreferrer">more</a>.

<blockquote>
<pre><code>&lt;asp:Label runat="server" ID="labelText" 
 ie:Text="This is IE text" 
 mozilla:Text="This is Firefox text" 
 Text="This is general text" 
/&gt;
</code></pre>
</blockquote>

That one kinda took me by surprise.

blocks|key|831290|text|System.Web.VirtualPathUtility|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|831291|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.virtualpathutility_methods.aspx^0|0|T|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]]]]

<a href="http://msdn.microsoft.com/en-us/library/system.web.virtualpathutility_methods.aspx" rel="nofollow noreferrer">System.Web.VirtualPathUtility</a>

blocks|key|1136373|text|我开发了一个asp.net应用程序，该应用程序通过了一家领先的安全公司的安全审计，我学到了这个简单的技巧来防止一个知名度较低但却很重要的安全漏洞。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1136374|下面的解释来自：攻击|offset|length|1136375|考虑使用Page.ViewStateUserKey来对抗一键攻击.如果对调用方进行身份验证并使用ViewState，请在Page_Init事件处理程序中设置Page.ViewStateUserKey属性以防止单击攻击。|1136376|void+Page_Init+(object+sender,+EventArgs+e)+{
++ViewStateUserKey+=+Session.SessionID;
}|code-block|syntax|javascript|1136377|将属性设置为每个用户都知道是唯一的值，例如会话ID、用户名或用户标识符。|1136378|当攻击者创建一个网页(.htm或.aspx)，其中包含一个名为__VIEWSTATE的隐藏表单字段，其中已经填充了ViewState数据，则会发生一次单击攻击。ViewState可以从攻击者以前创建的页面生成，比如带有100个条目的购物车页面。攻击者诱使不知情的用户浏览该页，然后将该页发送到ViewState有效的服务器。服务器无法知道ViewState起源于攻击者。ViewState验证和HMACs不抵抗这种攻击，因为ViewState是有效的，并且页面是在用户的安全上下文下执行的。|1136379|通过设置ViewStateUserKey属性，当攻击者浏览到页面以创建ViewState时，该属性将初始化为他或她的名称。当合法用户向服务器提交页面时，将使用攻击者的名称初始化该页面。结果，ViewState+HMAC检查失败，并生成异常。|1136380|entityMap|0|LINK|mutability|MUTABLE|url|http://www.guidanceshare.com/wiki/ASP.NET_2.0_Security_Guidelines_-_Parameter_Manipulation#Consider_Using_Page.ViewStateUserKey_to_Counter_One-Click_Attacks^0|0|8|2|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|16|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

I worked on a asp.net application which went through a security audit by a leading security company and I learned this easy trick to preventing a lesser known but important security vulnerability.

The below explanation is from:
<a href="http://www.guidanceshare.com/wiki/ASP.NET_2.0_Security_Guidelines_-_Parameter_Manipulation#Consider_Using_Page.ViewStateUserKey_to_Counter_One-Click_Attacks" rel="nofollow noreferrer">http://www.guidanceshare.com/wiki/ASP.NET_2.0_Security_Guidelines_-_Parameter_Manipulation#Consider_Using_Page.ViewStateUserKey_to_Counter_One-Click_Attacks</a>

Consider using Page.ViewStateUserKey to counter one-click attacks. If you authenticate your callers and use ViewState, set the Page.ViewStateUserKey property in the Page_Init event handler to prevent one-click attacks.

<pre><code>void Page_Init (object sender, EventArgs e) {
 ViewStateUserKey = Session.SessionID;
}
</code></pre>

Set the property to a value you know is unique to each user, such as a session ID, user name, or user identifier.

A one-click attack occurs when an attacker creates a Web page (.htm or .aspx) that contains a hidden form field named __VIEWSTATE that is already filled with ViewState data. The ViewState can be generated from a page that the attacker had previously created, such as a shopping cart page with 100 items. The attacker lures an unsuspecting user into browsing to the page, and then the attacker causes the page to be sent to the server where the ViewState is valid. The server has no way of knowing that the ViewState originated from the attacker. ViewState validation and HMACs do not counter this attack because the ViewState is valid and the page is executed under the security context of the user.

By setting the ViewStateUserKey property, when the attacker browses to a page to create the ViewState, the property is initialized to his or her name. When the legitimate user submits the page to the server, it is initialized with the attacker's name. As a result, the ViewState HMAC check fails and an exception is generated.

blocks|key|831286|text|HttpContext.Current.IsDebuggingEnabled|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|831287|这对于确定在dev中输出哪些脚本(min或完整版本)或其他可能想要的内容非常有用，但不适合使用。|831288|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.httpcontext.isdebuggingenabled.aspx^0|0|12|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

<a href="http://msdn.microsoft.com/en-us/library/system.web.httpcontext.isdebuggingenabled.aspx" rel="nofollow noreferrer">HttpContext.Current.IsDebuggingEnabled</a>

This is great for determining which scripts to output (min or full versions) or anything else you might want in dev, but not live.

blocks|key|1136133|text|包含在ASP.NET+3.5+SP1中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1136134|customErrors现在支持"redirectMode“属性，其值为"ResponseRewrite”。显示错误页而不更改URL。|unordered-list-item|1136135|form标记现在可以识别action属性。很适合当您使用URL重写时|1136136|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|K|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

Included in ASP.NET 3.5 SP1:

<ul>
<li>customErrors now supports "redirectMode" attribute with a value of "ResponseRewrite". Shows error page without changing URL.</li>
<li>The form tag now recognizes the action attribute. Great for when you're using URL rewriting</li>
</ul>

blocks|key|1136813|text|面板中的DefaultButton属性。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1136814|它设置特定面板的默认按钮。|1136815|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.panel.defaultbutton.aspx^0|4|D|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

<a href="http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.panel.defaultbutton.aspx" rel="nofollow noreferrer">DefaultButton</a> property in Panels.

It sets default button for a particular panel.

blocks|key|137125|text|ScottGu在http://weblogs.asp.net/scottgu/archive/2006/04/03/441787.aspx有很多窍门|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|137126|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/scottgu/archive/2006/04/03/441787.aspx^0|8|1P|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]]]]

ScottGu has a bunch of tricks at <a href="http://weblogs.asp.net/scottgu/archive/2006/04/03/441787.aspx" rel="nofollow noreferrer">http://weblogs.asp.net/scottgu/archive/2006/04/03/441787.aspx</a>

blocks|key|1137054|text|使用configSource拆分配置文件.|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1137055|例如，可以使用configSource文件中的web.config属性将配置元素推送到其他.config文件，而不是：|1137056|++++<appSettings>
++++++++<add+key="webServiceURL"+value="https://some/ws.url"+/>
++++++++
++++</appSettings>|code-block|syntax|javascript|1137057|...you可以将整个appSettings部分存储在另一个配置文件中。以下是新的web.config：|CODE|1137058|++++<appSettings+configSource="myAppSettings.config"+/>|1137059|myAppSettings.config文件：|1137060|++++<appSettings>++++++++
++++++++<add+key="webServiceURL"+value="https://some/ws.url"+/>
++++++++
++++</appSettings>|1137061|这对于将应用程序部署到客户并且不希望它们干扰web.config文件本身并且只希望它们能够更改几个设置的场景非常有用。|1137062|参考文献：http://weblogs.asp.net/fmarguerie/archive/2007/04/26/using-configsource-to-split-configuration-files.aspx|1137063|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/fmarguerie/archive/2007/04/26/using-configsource-to-split-configuration-files.aspx^0|0|L|0|0|0|15|A|0|0|0|K|0|0|0|5|2X|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1A|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1B|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1C|8|@$9|1D|A|1E|B|O]]|D|@]|E|$]]|$1|P|3|Q|5|J|7|1F|8|@]|D|@]|E|$K|L]]|$1|R|3|S|5|6|7|1G|8|@$9|1H|A|1I|B|O]]|D|@]|E|$]]|$1|T|3|U|5|J|7|1J|8|@]|D|@]|E|$K|L]]|$1|V|3|W|5|6|7|1K|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|1L|8|@]|D|@$9|1M|A|1N|1|1O]]|E|$]]|$1|Z|3|-4|5|6|7|1P|8|@]|D|@]|E|$]]]|10|$11|$5|12|13|14|E|$15|16]]]]

Using configSource to split configuration files.

You can use the configSource attribute in a web.config file to push configuration elements to other .config files, for example,
instead of:

<pre><code> &lt;appSettings&gt;
 &lt;add key="webServiceURL" value="https://some/ws.url" /&gt;
 &lt;!-- some more keys --&gt;
 &lt;/appSettings&gt;
</code></pre>

...you can have the entire appSettings section stored in another configuration file. Here's the new <code>web.config</code> : 

<pre><code> &lt;appSettings configSource="myAppSettings.config" /&gt;
</code></pre>

The <code>myAppSettings.config</code> file :

<pre><code> &lt;appSettings&gt; 
 &lt;add key="webServiceURL" value="https://some/ws.url" /&gt;
 &lt;!-- some more keys --&gt;
 &lt;/appSettings&gt;
</code></pre>

This is quite useful for scenarios where you deploy an application to a customer and you don't want them interfering with the web.config file itself and just want them to be able to change just a few settings.

ref: <a href="http://weblogs.asp.net/fmarguerie/archive/2007/04/26/using-configsource-to-split-configuration-files.aspx" rel="nofollow">http://weblogs.asp.net/fmarguerie/archive/2007/04/26/using-configsource-to-split-configuration-files.aspx</a>

blocks|key|137966|text|页面指令中的MaintainScrollPositionOnPostback属性。它用于在回发过程中维护aspx页面的滚动位置。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|137967|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.ui.page.maintainscrollpositiononpostback.aspx^0|6|W|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]]]]

<a href="http://msdn.microsoft.com/en-us/library/system.web.ui.page.maintainscrollpositiononpostback.aspx" rel="nofollow noreferrer">MaintainScrollPositionOnPostback</a> attribute in Page directive. It is used to maintain scroll position of aspx page across postbacks.

blocks|key|137005|text|HttpContext.IsCustomErrorEnabled是一个很酷的特性，我发现它不止一次有用。这是一个关于它的短柱。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|137006|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/leftslipper/archive/2008/07/13/httpcontext-iscustomerrorenabled-one-of-asp-net-s-hidden-gems.aspx^0|1O|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]]]]

HttpContext.IsCustomErrorEnabled is a cool feature.I've found it useful more than once. Here is a <a href="http://weblogs.asp.net/leftslipper/archive/2008/07/13/httpcontext-iscustomerrorenabled-one-of-asp-net-s-hidden-gems.aspx" rel="nofollow noreferrer">short post</a> about it.

blocks|key|834869|text|默认情况下，自定义控件的标记之间的任何内容都作为子控件添加。这可以在AddParsedSubObject()覆盖中被截获，用于过滤或附加解析(例如，LiteralControls中的文本内容)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|834870|++++protected+override+void+AddParsedSubObject(object+obj)
+++++{+var+literal+=+obj+as+LiteralControl;
+++++++if+(literal+!=+null)+Controls.Add(parseControl(literal.Text));
+++++++else+base.AddParsedSubObject(obj);
+++++}|code-block|syntax|javascript|834871|..。|834872|+++<uc:MyControl+runat='server'>
+++++...this+text+is+parsed+as+a+LiteralControl...
++</uc:MyControl>|834873|entityMap^0|Y|K|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

By default, any content between tags for a custom control is added as a child control. This can be intercepted in an AddParsedSubObject() override for filtering or additional parsing (e.g., of text content in LiteralControls):

<pre><code> protected override void AddParsedSubObject(object obj)
 { var literal = obj as LiteralControl;
 if (literal != null) Controls.Add(parseControl(literal.Text));
 else base.AddParsedSubObject(obj);
 }
</code></pre>

...

<pre><code> &lt;uc:MyControl runat='server'&gt;
 ...this text is parsed as a LiteralControl...
 &lt;/uc:MyControl&gt;
</code></pre>

blocks|key|831176|text|如果让ASP.NET生成RSS，它有时会在页面顶部增加一行。这不会用普通的RSS验证器进行验证。您可以通过在页面底部放置页面指令<@Page>来绕过它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|831177|entityMap^0|1S|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

If you have ASP.NET generating an RSS feed, it will sometimes put an extra line at the top of the page. This won't validate with common RSS validators. You can work around it by putting the page directive <code>&lt;@Page&gt;</code> at the bottom of the page.

blocks|key|1136118|text|在ASP.NET+v3.5添加路由之前，您可以创建自己的友好URL，只需在页面管道的早期向HTTPModule写入并重写请求(比如BeginRequest事件)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1136119|像http://servername/page/Param1/SomeParams1/Param2/SomeParams2这样的Urls将被映射到另一个页面，如下所示(通常使用正则表达式)。|offset|length|1136120|HttpContext.RewritePath("PageHandler.aspx?Param1=SomeParms1&Param2=SomeParams2");|code-block|syntax|javascript|1136121|DotNetNuke有一个非常好的HttpModule，可以为他们的友好urls做这件事。对于无法部署.NET+v3.5的机器仍然很有用。|1136122|entityMap|0|LINK|mutability|MUTABLE|url|http://servername/page/Param1/SomeParams1/Param2/SomeParams2^0|0|1|1O|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Before ASP.NET v3.5 added routes you could create your own friendly URLs simply by writing an HTTPModule to and rewrite the request early in the page pipeline (like the BeginRequest event).

Urls like <a href="http://servername/page/Param1/SomeParams1/Param2/SomeParams2" rel="nofollow noreferrer">http://servername/page/Param1/SomeParams1/Param2/SomeParams2</a> would get mapped to another page like below (often using regular expressions).

<pre><code>HttpContext.RewritePath("PageHandler.aspx?Param1=SomeParms1&amp;Param2=SomeParams2");
</code></pre>

DotNetNuke has a really good HttpModule that does this for their friendly urls. Is still useful for machines where you can't deploy .NET v3.5.

blocks|key|1136617|text|我的团队经常用这个作为黑客：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1136618|WebRequest+myRequest+=+WebRequest.Create("http://www.google.com");
WebResponse+myResponse+=+myRequest.GetResponse();
StreamReader+sr+=+new+StreamReader(myResponse.GetResponseStream());

//+here's+page's+response+loaded+into+a+string+for+further+use

String+thisReturn+=+sr.ReadToEnd().Trim();|code-block|syntax|javascript|1136619|它以字符串的形式加载网页的响应。您也可以发送post参数。|1136620|当我们需要便宜和快速的东西时，我们使用它来代替ASCX/AJAX/WebServices。基本上，它是跨服务器访问网络可用内容的一种快速方式。事实上，我们昨天刚刚把它命名为“”。|1136621|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

My team uses this a lot as a hack:

<pre><code>WebRequest myRequest = WebRequest.Create("http://www.google.com");
WebResponse myResponse = myRequest.GetResponse();
StreamReader sr = new StreamReader(myResponse.GetResponseStream());

// here's page's response loaded into a string for further use

String thisReturn = sr.ReadToEnd().Trim();
</code></pre>

It loads a webpage's response as a string. You can send in post parameters too. 

We use it in the place of ASCX/AJAX/WebServices when we need something cheap and fast. Basically, its a quick way to access web-available content across servers. In fact, we just dubbed it the "Redneck Web Service" yesterday.

blocks|key|138032|text|您知道在IIS或Visual之外运行ASP.Net是可能的吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|138033|整个运行时被打包并准备好托管在任何想要尝试它的进程中。使用ApplicationHost、HttpRuntime和HttpApplication类，您也可以研磨这些.aspx页面并从它们获得闪亮的HTML输出。|offset|length|style|CODE|138034|HostingClass+host+=+ApplicationHost.CreateApplicationHost(typeof(HostingClass),+
++++++++++++++++++++++++++++++++++++++++++++"/virtualpath",+"physicalPath");
host.ProcessPage(urlToAspxFile);+|code-block|syntax|javascript|138035|还有你的主持班：|138036|public+class+HostingClass+:+MarshalByRefObject
{
++++public+void+ProcessPage(string+url)
++++{
++++++++using+(StreamWriter+sw+=+new+StreamWriter("C:\temp.html"))
++++++++{
++++++++++++SimpleWorkerRequest+worker+=+new+SimpleWorkerRequest(url,+null,+sw);
++++++++++++HttpRuntime.ProcessRequest(worker);
++++++++}
++++++++++++++++++++//+Ta-dah!++C:\temp.html+has+some+html+for+you.
++++}
}|138037|entityMap^0|0|T|F|19|B|1L|F|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]|$D|W|E|X|F|G]|$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|12|8|@]|9|@]|A|$K|L]]|$1|Q|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|R|$]]

Did you know it's possible to run ASP.Net outside of IIS or Visual Studio?

The whole runtime is packaged up and ready to be hosted in any process that wants to give it a try. Using <code>ApplicationHost</code>, <code>HttpRuntime</code> and <code>HttpApplication</code> classes, you too can grind up those .aspx pages and get shiny HTML output from them.

<pre><code>HostingClass host = ApplicationHost.CreateApplicationHost(typeof(HostingClass), 
 "/virtualpath", "physicalPath");
host.ProcessPage(urlToAspxFile); 
</code></pre>

And your hosting class:

<pre><code>public class HostingClass : MarshalByRefObject
{
 public void ProcessPage(string url)
 {
 using (StreamWriter sw = new StreamWriter("C:\temp.html"))
 {
 SimpleWorkerRequest worker = new SimpleWorkerRequest(url, null, sw);
 HttpRuntime.ProcessRequest(worker);
 }
 // Ta-dah! C:\temp.html has some html for you.
 }
}
</code></pre>

blocks|key|1137113|text|CompilationMode=“永不”是一个在某些ASP.NET站点中可能至关重要的特性。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1137114|如果您有一个通过CMS或其他发布系统频繁生成和更新ASPX页面的ASP.NET应用程序，那么使用CompilationMode=“从不”是很重要的。|1137115|如果没有此设置，ASPX文件更改将触发重新编译，这将使您的appdomain重新启动。这可以消除会话状态和httpruntime缓存，更不用说重新编译所造成的滞后了。|1137116|(为了防止重新编译，可以增加numRecompilesBeforeAppRestart设置，但这并不理想，因为它消耗了更多的内存。)|1137117|对此特性的一个警告是，ASPX页面不能包含任何代码块。为了解决这个问题，可以将代码放在自定义控件和/或基类中。|1137118|在ASPX页面不经常更改的情况下，这个特性基本上是不相关的。|1137119|entityMap|0|LINK|mutability|MUTABLE|url|http://www.webpronews.com/expertarticles/2006/11/06/using-the-compilationmode-attribute-to-boost-performance|1|http://msdn.microsoft.com/en-us/library/s10awwz0.aspx^0|0|K|0|0|0|0|E|T|1|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|W]]]]

<a href="http://www.webpronews.com/expertarticles/2006/11/06/using-the-compilationmode-attribute-to-boost-performance" rel="nofollow">CompilationMode="Never"</a> is a feature which can be crucial in certain ASP.NET sites.

If you have an ASP.NET application where ASPX pages are frequently generated and updated via a CMS or other publishing system, it is important to use CompilationMode="Never".

Without this setting, the ASPX file changes will trigger recompilations which will quickly make your appdomain restart. This can wipe out session state and httpruntime cache, not to mention lag caused by recompilation.

(To prevent recompilation you could increase the <a href="http://msdn.microsoft.com/en-us/library/s10awwz0.aspx" rel="nofollow">numRecompilesBeforeAppRestart</a> setting, but that is not ideal as it consumes more memory.)

One caveat to this feature is that the ASPX pages cannot contain any code blocks. To get around this, one may place code in custom controls and/or base classes.

This feature is mostly irrelevant in cases where ASPX pages don't change often.

blocks|key|1136315|text|VS所用的有效语法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1136316|<input+type="checkbox"+name="roles"+value='<%25#+Eval("Name")+%25>'+
++<%25#+((bool)+Eval("InRole"))+?+"checked"+:+""+%25>+
++<%25#+ViewData.Model.IsInRole("Admin")+?+""+:+"disabled"+%25>+/>|code-block|syntax|javascript|1136317|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Valid syntax that VS chokes on:

<pre><code>&lt;input type="checkbox" name="roles" value='&lt;%# Eval("Name") %&gt;' 
 &lt;%# ((bool) Eval("InRole")) ? "checked" : "" %&gt; 
 &lt;%# ViewData.Model.IsInRole("Admin") ? "" : "disabled" %&gt; /&gt;
</code></pre>

blocks|key|137640|text|System.Web.Hosting.HostingEnvironment.MapPath|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|137641|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.hosting.hostingenvironment.mappath.aspx^0|0|19|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]]]]

<a href="http://msdn.microsoft.com/en-us/library/system.web.hosting.hostingenvironment.mappath.aspx" rel="nofollow noreferrer">System.Web.Hosting.HostingEnvironment.MapPath</a>

blocks|key|137675|text|我想到了一个特性，有时你需要把页面的某些部分隐藏起来，不让乌鸦看到。您可以使用javascript或使用以下简单代码进行此操作：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|137676|if+(Request.Browser.Crawler){
++++++++HideArticleComments();|code-block|syntax|javascript|137677|entityMap^0|13|A|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

one feature came to my mind, sometimes you will need to hide some part of your page from the crowlers. you can do it with javascript or using this simple code:

<pre><code>if (Request.Browser.Crawler){
 HideArticleComments();
</code></pre>

blocks|key|137993|text|类似于optimizeCompilations=的“真”解决方案，这里的另一个解决方案可以加快您在构建之间等待的时间(特别是当您正在处理大型项目时)：创建一个基于ram的驱动器(即使用RamDisk)，并将默认的“临时ASP.NET文件”更改为基于内存的驱动器.。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|137994|关于如何做到这一点的全部细节见我的博客：http://www.wagnerdanda.me/2009/11/speeding-up-build-times-in-asp-net-with-ramdisk/|137995|基本上，您首先配置一个RamDisk+(同样，在我的博客中有一个指向免费磁盘的链接)，然后根据以下内容更改您的web.config：|137996|+<system.web>
+....
+++++<compilation+debug="true"+tempDirectory="R:\ASP_NET_TempFiles\">
+++++....
+++++</compilation>
+....
+</system.web>|code-block|syntax|javascript|137997|它大大增加了我的开发时间，您只需要为您的计算机投资内存:)|137998|编程愉快！|137999|瓦格纳·丹达|138000|entityMap|0|LINK|mutability|MUTABLE|url|http://www.wagnerdanda.me/2009/11/speeding-up-build-times-in-asp-net-with-ramdisk/^0|0|1F|23|1K|0|K|2A|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|17|8|@]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|H|3|I|5|6|7|1B|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1C|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1D|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1E|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1F|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]]]

Similarly to the optimizeCompilations=”true” solution, here another one to speed up the time you spend waiting in between builds (very good especially if you are working with a large project): create a ram-based drive (i.e. using RamDisk) and change your default “Temporary ASP.NET Files” to this memory-based drive.

The full details on how to do this is on my blog: <a href="http://www.wagnerdanda.me/2009/11/speeding-up-build-times-in-asp-net-with-ramdisk/" rel="nofollow noreferrer">http://www.wagnerdanda.me/2009/11/speeding-up-build-times-in-asp-net-with-ramdisk/</a>

Basically you first and configure a RamDisk (again, in my blog there a link to a free ramdisk) and then you change your web.config according to this:

<pre><code> &lt;system.web&gt;
 ....
 &lt;compilation debug="true" tempDirectory="R:\ASP_NET_TempFiles\"&gt;
 ....
 &lt;/compilation&gt;
 ....
 &lt;/system.web&gt;
</code></pre>

It greatly increase my development time, you just need invest in memory for you computer :)

Happy Programming!

Wagner Danda

blocks|key|1136068|text|当我将一个xmlDocument()转储到一个标签中，并使用它的xsl转换显示它时，我认为它是很整洁的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1136069|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 thought it was neat when I dumped a xmlDocument() into a label and it displayed using it's xsl transforms.

blocks|key|1136790|text|Request.IsLocal属性：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1136791|它指示当前请求是否来自本地计算机。|1136792|if(+Request.IsLocal+)
{
+++LoadLocalAdminMailSettings();
}
else
{
+++LoadServerAdminMailSettings();
}|code-block|syntax|javascript|1136793|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.httprequest.islocal.aspx^0|0|I|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

<a href="http://msdn.microsoft.com/en-us/library/system.web.httprequest.islocal.aspx" rel="nofollow noreferrer">Request.IsLocal Property :</a>

It indicates whether current request is coming from Local Computer or not. 

<pre><code>if( Request.IsLocal )
{
 LoadLocalAdminMailSettings();
}
else
{
 LoadServerAdminMailSettings();
}
</code></pre>

blocks|key|1137170|text|默认情况下，任何网页都是从System.Web.UI.Page类继承的。如果您希望从从System.Web.UI.Page继承的自定义基类继承页面，怎么办？|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1137171|有一种方法可以约束从您自己的基类继承的任何页面。只需在web.config上添加一条新行|1137172|<system.web>
++++<pages+pageBaseType="MyBasePageClass"+/>
</system.web>|code-block|syntax|javascript|1137173|警告:只有当你的课是独立的，这才是有效的。我指的是一个没有代码隐藏的类，它看起来像<%25@+Page+Language="C#"+AutoEventWireup="true"+%25>。|1137174|entityMap^0|D|I|17|I|0|R|A|0|0|15|1C|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|P|$]]

By default any web form page inherits from <code>System.Web.UI.Page</code> class. What if you want your pages to inherit from a custom base class, which inherits from <code>System.Web.UI.Page</code>? 

There is a way to constraint any page to inherit from your own base class. Simply add a new line on your <code>web.config</code>:

<pre><code>&lt;system.web&gt;
 &lt;pages pageBaseType="MyBasePageClass" /&gt;
&lt;/system.web&gt;
</code></pre>

Caution: this is only valid if your class is a stand-alone one. I mean a class that has no code-behind, which looks like <code>&lt;%@ Page Language="C#" AutoEventWireup="true" %&gt;</code>

blocks|key|834976|text|将位于App_Code文件夹中的类附加到全局应用程序类文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|834977|ASP.NET+2.0+-+Global.asax+-文件背后的代码。|offset|length|834978|这也适用于2008。|834979|entityMap|0|LINK|mutability|MUTABLE|url|http://aspadvice.com/blogs/kiran/archive/2005/12/11/14301.aspx^0|0|0|Y|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Attach a class located in your App_Code folder to your Global Application Class file.

<a href="http://aspadvice.com/blogs/kiran/archive/2005/12/11/14301.aspx" rel="nofollow noreferrer">ASP.NET 2.0 - Global.asax - Code Behind file</a>.

This works in Visual Studio 2008 as well.

blocks|key|137700|text|EnsureChildControls法：它检查子控件是否已启动。如果子控件未启动，则调用CreateChildControls方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|137701|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.ui.control.ensurechildcontrols.aspx^0|0|K|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]]]]

<a href="http://msdn.microsoft.com/en-us/library/system.web.ui.control.ensurechildcontrols.aspx" rel="nofollow noreferrer">EnsureChildControls Method</a> : It checks the child controls if they're initiated. If the child controls are not initiated it calls CreateChildControls method.

blocks|key|1136210|text|可以通过使用其UniqueID属性找到任何控件：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1136211|Label+label+=+(Label)Page.FindControl("UserControl1$Label1");|code-block|syntax|javascript|1136212|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.ui.control.uniqueid.aspx^0|7|8|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

You can find any control by using its <a href="http://msdn.microsoft.com/en-us/library/system.web.ui.control.uniqueid.aspx" rel="nofollow noreferrer">UniqueID</a> property:

<pre><code>Label label = (Label)Page.FindControl("UserControl1$Label1");
</code></pre>

blocks|key|835373|text|很多人提到了如何在重新编译时优化代码。最近，我发现我可以在aspx页面中完成我的大部分开发(代码隐藏部分)，并且完全跳过构建步骤。只需保存文件并刷新页面即可。您所要做的就是将代码包装在以下标记中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|835374|<script+runat="server">

+++Protected+Sub+Page_Load(ByVal+sender+As+Object,+ByVal+e+As+System.EventArgs)+Handles+Me.Load
+++++Response.Write("Look+Ma',+I+didn't+even+had+to+build!")
+++End+Sub

</script>|code-block|syntax|javascript|835375|一旦你完成了，只需移动所有的代码-隐藏，构建，测试所有的工作和瞧！|835376|-D|835377|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Lots of people mentioned how to optimize your code when recompiling. Recently I discovered I can do most of my development (code-behind stuff) in the aspx page and skipping completely the build step. Just save the file and refresh your page. All you have to do is wrap your code in the following tag:

<pre><code>&lt;script runat="server"&gt;

 Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
 Response.Write("Look Ma', I didn't even had to build!")
 End Sub

&lt;/script&gt;
</code></pre>

Once you are done, Just move all to the code-behind, build, test everything works and voila!

-D

blocks|key|137580|text|页对象上的ClientScript属性。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|137581|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/3hc29e2a.aspx^0|5|C|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]]]]

<a href="http://msdn.microsoft.com/en-us/library/3hc29e2a.aspx" rel="nofollow noreferrer">ClientScript</a> property on Page object.

blocks|key|835357|text|如果您使用web服务而不是WCF服务，您仍然可以使用标准的System.Web.Security.FormsAuthentication.SetAuthCookie(userName，成员资格在集合web服务上强制执行身份验证和登录会话行为，类似于您将如何使用成员资格表单身份验证来保护网站&当然，在调用Membership.ValidateUser(userName，密码)之后调用Membership.ValidateUser(userName，password)之后，不需要通过调用Membership.ValidateUser(userName，password)来实现特殊会话和/或soap头实现，这样就可以在响应中创建cookie，就好像用户已经通过web表单登录一样。然后，您可以使用Response.Cookies[].Value检索此身份验证cookie，并将其作为字符串返回给用户，该字符串可用于在随后的调用中通过提取Application_BeginRequest中的cookie重新创建cookie来验证用户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|835358|cookie方法从Request.InputStream调用param并在成员身份验证请求之前重新创建auth，这样成员资格提供程序就会被欺骗，并且知道请求是经过身份验证的，并强制执行其所有规则。|835359|将此cookie返回给用户的示例web方法签名为:+string+(userName，密码)|835360|后续的web方法调用示例是:+string+DoSomething(string+authcookie、string+methodParam1、int+methodParam2等)，其中您需要从Request.InputStreamis中提取authcookie(即从Login方法获得的值)+param。|835361|这还会模拟登录会话，并在类似于此登录(Authcookie)的web方法中调用FormsAuthentication.SignOut，从而使用户需要再次登录。|835362|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

If you use web services instead WCF services, you can still use standard .Net membership to enforce authentication and login session behaviour
on a set web services similarly to a how you would secure web site with membership forms authentication &amp; without the need for a special session
and/or soap headers implementations by simply calling System.Web.Security.FormsAuthentication.SetAuthCookie(userName, false) [after calling
Membership.ValidateUser(userName, password) of course] to create cookie in the response as if the user has logged in via a web form.
Then you can retrieve this authentication cookie with Response.Cookies[].Value and return it as a string to the user
which can be used to authenticate the user in subsequent calls by re-creating the cookie in the Application_BeginRequest by extracting the 
cookie method call param from the Request.InputStream and re-creating the auth cookie before the membership authenticates the request this way the
membership provider gets tricked and will know the request is authenticated and enforce all its rules. 

Sample web method signature to return this cookie to the user would be:
string Login(userName,password) 

Sample subsequent web method call would be:
string DoSomething(string authcookie,string methodParam1,int methodParam2 etc,etc) where you need to extract authcookie(which is value obtained from Login method) param from the Request.InputStreamis 

This also simulates a login session and calling FormsAuthentication.SignOut in a web method like this Logout(authcookie) would
make the user need to sign in again.

blocks|key|138195|text|“档案”属性在web.config中的element元素上。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|138196|指定包含自定义应用程序配置设置的外部文件的相对路径。|138197|如果在许多需要在不同环境(prod)上进行修改的应用程序设置中，很少有应用程序设置，这是一个很好的选择。|138198|由于对Web.config文件的任何更改都会导致应用程序重新启动，因此使用单独的文件允许用户修改appSettings部分中的值，而不会导致应用程序重新启动。单独文件的内容与appSettings文件中的Web.config部分合并。|138199|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms228154.aspx^0|0|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

<a href="http://msdn.microsoft.com/en-us/library/ms228154.aspx" rel="nofollow">'file'</a> attribute on appsettings element in web.config.

Specifies a relative path to an external file that contains custom application configuration settings.

If you have few app settings out of many that need to modified on different environments (prod), this is excellent choice. 

Because any changes to the Web.config file cause the application to restart, using a separate file allows users to modify values that are in the appSettings section without causing the application to restart. The contents of the separate file are merged with the appSettings section in the Web.config file.

blocks|key|138151|text|应用程序变量可以与web应用程序一起使用，以便在整个应用程序之间进行通信。它在Global.asax文件中初始化，并由独立于它们创建的会话的所有用户在web应用程序中的页面上使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|138152|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|$]]

Application variables can be used with web application for communicating across the whole application. It is initialized in Global.asax file and used over the pages in that web application by all the user independent of the session they create.

blocks|key|1137141|text|可以将ASPX页面打包到库(.dll)中，并与ASP.NET引擎一起服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1137142|您将需要实现您自己的VirtualPathProvider，它将通过特定的DLL来加载，或者您可以在路径名中包含DLL名称。由你决定。|offset|length|1137143|当重写VirtualFile.Open方法时，就会发生这种神奇的情况，您将ASPX文件作为来自Assembly：Assembly.GetManifestResourceStream的资源返回。ASP.NET引擎将处理资源，因为它是通过VirtualPathProvider服务的。|1137144|这允许插入页面，或者像我一样，使用它来包含带有控件的HttpHandler。|1137145|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.hosting.virtualpathprovider.aspx|1|http://msdn.microsoft.com/en-us/library/system.web.hosting.virtualfile.open.aspx|2|http://msdn.microsoft.com/en-us/library/xc4235zt.aspx^0|0|A|J|0|0|3|G|1|1K|Y|2|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@$D|11|E|12|1|13]|$D|14|E|15|1|16]]|A|$]]|$1|H|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]|T|$5|M|N|O|A|$P|U]]]]

It's possible to package ASPX pages into a Library (.dll), and serve them with the ASP.NET engine.

You will need to implement your own <a href="http://msdn.microsoft.com/en-us/library/system.web.hosting.virtualpathprovider.aspx" rel="nofollow">VirtualPathProvider</a>, which will load via Relfection specific DLL's, or you could include the DLL name in your pathname. It's up to you.

The magic happens when overriding the <a href="http://msdn.microsoft.com/en-us/library/system.web.hosting.virtualfile.open.aspx" rel="nofollow">VirtualFile.Open</a> method, where you return the ASPX file as a resource from the Assembly class: <a href="http://msdn.microsoft.com/en-us/library/xc4235zt.aspx" rel="nofollow">Assembly.GetManifestResourceStream</a>. The ASP.NET engine will process the resource since it is served via the VirtualPathProvider.

This allows to plug-in pages, or like I did, use it to include a HttpHandler with a control.

blocks|key|138345|text|模板用户控件。一旦你知道了它们的工作原理，你就会看到各种各样的可能性。以下是最简单的实现：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|138346|TemplatedControl.ascx|style|BOLD|138347|这里最棒的事情是使用简单而熟悉的用户控件构建块，并能够使用HTML和一些占位符来布局UI的不同部分。|138348|<%25@+Control+Language="C#"+CodeFile="TemplatedControl.ascx.cs"+Inherits="TemplatedControl"+%25>

<div+class="header">
++++<asp:PlaceHolder+ID="HeaderPlaceHolder"+runat="server"+/>
</div>
<div+class="body">
++++<asp:PlaceHolder+ID="BodyPlaceHolder"+runat="server"+/>
</div>|code-block|syntax|javascript|138349|TemplatedControl.ascx.cs|138350|这里的“秘密”是使用ITemplate类型的公共属性，并了解[ParseChildren]和[PersistenceMode]属性。|CODE|138351|using+System.Web.UI;

[ParseChildren(true)]
public+partial+class+TemplatedControl+:+System.Web.UI.UserControl
{
++++[PersistenceMode(PersistenceMode.InnerProperty)]
++++public+ITemplate+Header+{+get;+set;+}

++++[PersistenceMode(PersistenceMode.InnerProperty)]
++++public+ITemplate+Body+{+get;+set;+}

++++void+Page_Init()
++++{
++++++++if+(Header+!=+null)
++++++++++++Header.InstantiateIn(HeaderPlaceHolder);

++++++++if+(Body+!=+null)
++++++++++++Body.InstantiateIn(BodyPlaceHolder);
++++}
}|138352|Default.aspx|138353|<%25@+Register+TagPrefix="uc"+TagName="TemplatedControl"+Src="TemplatedControl.ascx"+%25>

<uc:TemplatedControl+runat="server">
++++<Header>Lorem+ipsum</Header>
++++<Body>
++++++++//+You+can+add+literal+text,+HTML+and+server+controls+to+the+templates
++++++++Hello+<asp:Label+runat="server"+Text="world"+/>!
++++</Body>
</uc:TemplatedControl>|138354|您甚至可以获得内部模板属性的IntelliSense。因此，如果您在一个团队中工作，您可以快速创建可重用的UI，以实现您的团队已经享受到的与内置ASP.NET服务器控件相同的可组合性。|138355|MSDN示例+(与开头相同的链接)添加了一些额外的控件和一个命名容器，但只有当您想支持“中继器类型”控件时，才需要这样做。|138356|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/36574bf6%2528v=VS.100%2529.aspx|1|http://msdn.microsoft.com/en-us/library/system.web.ui.parsechildrenattribute.aspx|2|http://msdn.microsoft.com/en-us/library/system.web.ui.persistencemodeattribute.aspx|3|http://msdn.microsoft.com/en-us/library/36574bf6.aspx^0|0|6|0|0|0|L|0|0|0|0|O|0|A|9|U|F|1A|H|U|F|1|1A|H|2|0|0|0|C|0|0|0|0|6|3|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@$A|1I|B|1J|1|1K]]|C|$]]|$1|D|3|E|5|6|7|1L|8|@$A|1M|B|1N|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|1O|8|@]|9|@]|C|$]]|$1|J|3|K|5|L|7|1P|8|@]|9|@]|C|$M|N]]|$1|O|3|P|5|6|7|1Q|8|@$A|1R|B|1S|F|G]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1T|8|@$A|1U|B|1V|F|S]|$A|1W|B|1X|F|S]|$A|1Y|B|1Z|F|S]]|9|@$A|20|B|21|1|22]|$A|23|B|24|1|25]]|C|$]]|$1|T|3|U|5|L|7|26|8|@]|9|@]|C|$M|N]]|$1|V|3|W|5|6|7|27|8|@$A|28|B|29|F|G]]|9|@]|C|$]]|$1|X|3|Y|5|L|7|2A|8|@]|9|@]|C|$M|N]]|$1|Z|3|10|5|6|7|2B|8|@]|9|@]|C|$]]|$1|11|3|12|5|6|7|2C|8|@]|9|@$A|2D|B|2E|1|2F]]|C|$]]|$1|13|3|-4|5|6|7|2G|8|@]|9|@]|C|$]]]|14|$15|$5|16|17|18|C|$19|1A]]|1B|$5|16|17|18|C|$19|1C]]|1D|$5|16|17|18|C|$19|1E]]|1F|$5|16|17|18|C|$19|1G]]]]

<a href="http://msdn.microsoft.com/en-us/library/36574bf6%28v=VS.100%29.aspx" rel="nofollow">Templated user controls</a>. Once you know how they work you will see all sorts of possibilities. Here's the simplest implementation:

TemplatedControl.ascx

The great thing here is using the easy and familiar user control building block and being able to layout the different parts of your UI using HTML and some placeholders.

<pre><code>&lt;%@ Control Language="C#" CodeFile="TemplatedControl.ascx.cs" Inherits="TemplatedControl" %&gt;

&lt;div class="header"&gt;
 &lt;asp:PlaceHolder ID="HeaderPlaceHolder" runat="server" /&gt;
&lt;/div&gt;
&lt;div class="body"&gt;
 &lt;asp:PlaceHolder ID="BodyPlaceHolder" runat="server" /&gt;
&lt;/div&gt;
</code></pre>

TemplatedControl.ascx.cs

The 'secret' here is using public properties of type <code>ITemplate</code> and knowing about the <a href="http://msdn.microsoft.com/en-us/library/system.web.ui.parsechildrenattribute.aspx" rel="nofollow"><code>[ParseChildren]</code></a> and <a href="http://msdn.microsoft.com/en-us/library/system.web.ui.persistencemodeattribute.aspx" rel="nofollow"><code>[PersistenceMode]</code></a> attributes.

<pre><code>using System.Web.UI;

[ParseChildren(true)]
public partial class TemplatedControl : System.Web.UI.UserControl
{
 [PersistenceMode(PersistenceMode.InnerProperty)]
 public ITemplate Header { get; set; }

 [PersistenceMode(PersistenceMode.InnerProperty)]
 public ITemplate Body { get; set; }

 void Page_Init()
 {
 if (Header != null)
 Header.InstantiateIn(HeaderPlaceHolder);

 if (Body != null)
 Body.InstantiateIn(BodyPlaceHolder);
 }
}
</code></pre>

Default.aspx

<pre><code>&lt;%@ Register TagPrefix="uc" TagName="TemplatedControl" Src="TemplatedControl.ascx" %&gt;

&lt;uc:TemplatedControl runat="server"&gt;
 &lt;Header&gt;Lorem ipsum&lt;/Header&gt;
 &lt;Body&gt;
 // You can add literal text, HTML and server controls to the templates
 &lt;p&gt;Hello &lt;asp:Label runat="server" Text="world" /&gt;!&lt;/p&gt;
 &lt;/Body&gt;
&lt;/uc:TemplatedControl&gt;
</code></pre>

You will even get IntelliSense for the inner template properties. So if you work in a team you can quickly create reusable UI to achieve the same composability that your team already enjoys from the built-in ASP.NET server controls.

The <a href="http://msdn.microsoft.com/en-us/library/36574bf6.aspx" rel="nofollow">MSDN example</a> (same link as the beginning) adds some extra controls and a naming container, but that only becomes necessary if you want to support 'repeater-type' controls.

blocks|key|1135818|text|这似乎是个又大又模糊的问题..。但我会投入反思，因为它让我做了一些不可思议的强大的事情，如可插拔的数据和诸如此类。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1135819|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|$]]

This seems like a huge, vague question... 
But I will throw in Reflection, as it has allowed me to do some incredibly powerful things like pluggable DALs and such.

blocks|key|138128|text|在网站发布并部署到生产服务器后，如果需要对服务器端按钮进行一些更改，请单击事件。我们可以在aspx页面本身中使用new关键字来覆盖现有的单击事件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|138129|示例|138130|方法后面的代码|138131|+Protected+void+button_click(sender+object,+e+System.EventArgs)+
++{
+++++Response.Write("Look+Ma',+I+Am+code+behind+code!")++
++}|code-block|syntax|javascript|138132|OverRided方法：|BOLD|138133|<script+runat="server">+++
+++Protected+void+new+button_click(sender+object,+e+System.EventArgs)+
++{
+++++Response.Write("Look+Ma',+I+am+overrided+method!")++
++}

</script|138134|通过这种方式，我们可以轻松地修复生产服务器错误，而无需重新部署。|138135|entityMap^0|1K|3|0|0|0|0|0|C|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|12|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|13|8|@$9|14|A|15|B|Q]]|D|@]|E|$]]|$1|R|3|S|5|L|7|16|8|@]|D|@]|E|$M|N]]|$1|T|3|U|5|6|7|17|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|W|$]]

After the website was published and deployed in the production server, If we need to do some changes on the server side button click event. We can override the existing click event by using the <code>new</code>keyword in the aspx page itself.

Example

Code Behind Method

<pre><code> Protected void button_click(sender object, e System.EventArgs) 
 {
 Response.Write("Look Ma', I Am code behind code!") 
 }
</code></pre>

OverRided Method:

<pre><code>&lt;script runat="server"&gt; 
 Protected void new button_click(sender object, e System.EventArgs) 
 {
 Response.Write("Look Ma', I am overrided method!") 
 }

&lt;/script
</code></pre>

In this way we can easily fix the production server errors without redeployment.

<blockquote>
 This question exists because it has
 historical significance, but it is not
 considered a good, on-topic question
 for this site, so please do not use it
 as evidence that you can ask similar
 questions here.
 
 More info: <a href="https://stackoverflow.com/faq">https://stackoverflow.com/faq</a>
</blockquote>

<hr>

There are always features that would be useful in fringe scenarios, but for that very reason most people don't know them. I am asking for features that are not typically taught by the text books.

What are the ones that you know?

Hidden Features of ASP.NET

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

这个问题之所以存在，是因为它具有历史意义，但对于这个网站来说，它并不是一个很好的主题问题，所以请不要用它作为你可以在这里提出类似问题的证据。更多信息：在边缘场景中，总会有一些有用的特性，但正是因为这个原因，大多数人并不了解它们。我要求的功能，通常不是教的教科书。你知道的是什么？

问ASP.NET的隐藏特征
EN

回答 52

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET的隐藏特征EN

回答 52

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET的隐藏特征
EN