Last post Mar 31, 2010 05:07 AM by rickliveshere
Mar 31, 2010 05:07 AM|rickliveshere|LINK
I recently came across an issue while developing an asynchronous handler based upon the guides available on MSDN:
According to my understanding of the guides, you are able to create a base handler that child classes may inherit from. These child classes can then be called from the base handler via a delegate as part of an asynchronous operation. In my project, there
is a root web.config for common app settings, and each set of child classes have their own web.config assigned for overridden settings.
My problem arises when one of the child classes attempts to read an overridden app setting from a local web.config. Debugging has revealed the base handler is able to access both common and overridden app settings via the ConfigurationManager class. However
as soon as an asynchcronous call to a child class is made, the ConfigurationManager can only access app settings from the root web.config.
Googling the problem appears to indicate that overridden app settings from a child configuration file are lost as soon as an asynchronous call is made. Suggested solutions have been to either pass down any overridden app settings required by child classes
down from the base handler, or specify a set of location tags in the root config in place of child configuration files.
Has anybody else come across this issue, and did you find any alternative solutions? My project is based on .NET 2.0