ASP.NET Diagnostic Page to Dump ASP.NET and Environment Configuration

<%@ Page Language="C#" AutoEventWireup="true" Trace="true" TraceMode="SortByCategory" %>
<html xmlns="">
<head runat="server">
  <title>ASP.NET Diagnostic Page</title>
  <form id="form1" runat="server">
  <h2>Environment Variables</h2>
    var variables = Environment.GetEnvironmentVariables();
    foreach (DictionaryEntry entry in variables)

  Response.Filter = <%= Request.Filter.ToString() %>
  Request.ApplicationPath = <%= Request.ApplicationPath %>
  Request.PhysicalApplicationPath = <%= Request.PhysicalApplicationPath %>
  Request.PhysicalPath = <%= Request.PhysicalPath %>
  Request.UrlReferrer = <%= Request.UrlReferrer %>
  Request.UserLanguages = <%= string.Join(",", (Request.UserLanguages ?? new string[0])) %>


File Attribute And Things To Remember

If you wanted to include another .config file within your websites web.config you can reference it as a property of


<appSettings file="appconfig\custselfserv\custselfserv.config">

Note that appconfig\custom\secretconfig.config is relative to the root of your website.

Including extra configuration files are useful for cases where you want to lock down production process ID’s and other secret settings. You can grant your production management team and IIS access to /appconfig which would conceal the settings from being read by say developers.

One thing to remember is if you change settings in this included file the IIS app pool will need to be refreshed for the changes to be picked up. web.config changes will induce an app pool refresh however included files will not automatically.