No exceptions of the ConfigurationException type are thrown when you run a .NET Framework 2.0-based application

When you run a Microsoft .NET Framework 2.0-based application, you may notice that no exceptions of the ConfigurationException type are thrown. This behavior occurs even if the .config file is missing or if the .config file contains configuration settings that are not valid.

Typically, this behavior occurs if the following conditions are true:

• An assembly is executed by using the AppDomain object.
• The AppDomain object is created by using the AppDomainSetup object.
• The ConfigurationFile property for the AppDomainSetup object uses a URL that disallows anonymous access to the executed assembly.

This behavior occurs because the configuration system in the .NET Framework 2.0 ignores errors when the configuration system loads .config files over the network. This behavior prevents a malicious user from acquiring detailed information in exceptions.

This behavior is by design.

For more information, visit the following Microsoft Developer Network (MSDN) Web sites: