Multiple Web.Config files - from a code point-of-view
<p>ASP.NET allows for Web.Config files at sub-levels within a site structure. However, I can't find any articles discussing how this looks from code.</p>

<p>In the Orchard CMS there are config files all over the shop. There's even a config file in a folder containing only .CSS files! I'm new to larger-scale ASP.NET apps so...</p>

<p>Can someone just tell me if I'm right in my assumptions.</p>

<ul>
<li><p>The config file can affect server settings, and hence how a server processes a request to a resource further down a site structure.</p></li>
<li><p>From a code point of view, if the same line of code in the same class queries the config file during a request for <code>http://level1.resource</code> then it could read a different value to when the same code executes during a request for <code>http://level1/level2.resource</code> (if there is a web.config at level2)</p>

<ul>
<li>Overall, the way it works is based on the current request path.</li>
</ul></li>
</ul>

<p>Right?</p>
