  
 |
If you are running the .NET IDK as a web application that hosts web services (that do not use the logging API), the Web.config file is the best way to configure log instrumentation.
The IDK Web.config follows the normal precedence rules of IIS Web.config: within a web application, machine.config is read first for configuration values, then overlaid with Web.config from each parent directory within the web application subtree down to the directory containing the running code. The example below shows the logging settings only.
All .NET web applications have Web.config files. If the configuration file does not have an <appSettings> section, it can be added along with the key-value pairs to configure logging.
<configuration>
<appSettings>
<add key="ptedk.LoggingApplicationName" value="Bulk-Document-Loader" />
<add key="ptedk.LogToNetwork" value="true" />
<add key="ptedk.VerboseLogging" value="true" />
</appSettings>
<system.web>
...
</system.web>
</configuration>
For stand-alone .NET applications outside a Web application
context, use programmatic configuration. For details, see Using IDK Logging in .NET.
   |