However, folders and applications can rely on virtual directories. When you use a virtual
directory for the folder or application, the Web.CONFIG file appears in the root folder of that
virtual directory. Again, even though the Windows hierarchy differs from the Web server hierarchy,
the Web server hierarchy is the one that matters. Folder and application Web.CONFIG file settings
always override those of the Web site and the Web server.
An Overview of the Web.CONFIG Elements
It??™s time to put a number of puzzle pieces together to obtain a better understanding of how things
work with the Web.CONFIG file. The important issue to remember is that only changed items appear
in the Web.CONFIG file. For example, if you create a trace log entry for the Default Web Site using the
AppCmd utility (type AppCmd Configure TRACE ???Default Web Site/??? /enable /path:*.ASP
/timeTaken:???00:01:00??? /verbosity:Warning and press Enter to see this example), Web.CONFIG
file for the Default Web site will look like Listing 25.1.
Listing 25.1: Creating a CONFIG File Entry for a Trace
Pages:
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319