ASP.NET Web.Config Hidden Features? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers. 开发者_JS百科

---

Want to improve this question? Update the question so it focuses on one problem only by editing this post.

Closed 8 years ago.

Improve this question

Yesterday I found a very useful article on MSDN about Enabling Application-Level Tracing http://msdn.microsoft.com/en-us/library/1y89ed7z(VS.85).aspx

<configuration>
 <system.web>
  <trace enabled="true" requestLimit="40" localOnly="false"/>
 </system.web>
</configuration>

So I would to ask if there are other useful config settings that you recommend learning about?

---

See here and the pages it links to (and the pages those pages link to) to explore various things you can put into web.config. http://msdn.microsoft.com/en-us/library/ms228147(v=VS.85).aspx

---

There are technically no undocumented features of the web.config that you should use, and that trace feature is documented.

However, this page may help you: http://msdn.microsoft.com/en-us/library/1fk1t1t0(v=VS.85).aspx or this one http://msdn.microsoft.com/en-us/library/dayb112d(v=VS.85).aspx

As well as checking the .config files in C:\Windows\System32\inetsrv\config and C:\Windows\Microsoft.NET\Framework\v2.0.50727

All the features that you primarily will use are configured in those files or listed as a topic or linked topic on that Microsoft page I linked you earlier.

---

For one, there is the web.debug.config and web.release.config.
And there is also a practice of encrypting connectionstrings in web.config