Re: [Netcommon-developer] common logging configuration section reading on starting from network share failure

[Stephen B. <sb...@gm...>]

Interesting...we'll probably just change the core code so that we're
invoking the 'recommended workaround' code-path of
System.Configuration.Configuration.GetSection(sectionName)
instead of relying upon the ConfigurationManager to do the work.  Other
than this issue report, we've seen no additional issues reported from the
M1 milestone release bits so I think we'll go to 2.1 GA by the end of the
week after making this change.

Thanks for the reported issue!~

Steve Bohlen
sb...@gm...
http://blog.unhandled-exceptions.com
http://twitter.com/sbohlen


On Thu, May 31, 2012 at 9:25 AM, cosmin dumitru <du...@gm...> wrote:

> Hi,****
>
> ** **
>
> I have following problem found : Security exception on configuration
> reading when the application it is started from network share failure.****
>
> I try the basiclogging project using the EnterpriseLibrary ****
>
> ** **
>
> The only difference is that I use the outside definition of common logging
> configuration sections, that on local folder works without problems.****
>
> ** **
>
> <common>****
>
> <logging configSource="CommonLogging.Config" />****
>
> </common>****
>
> ** **
>
> The exception comes on
> return ConfigurationManager.GetSection(sectionName); in
> defaultconfigutrationreadder.cs.****
>
> The problem it is an bug in System.Configuration described in *
> http://support.microsoft.com/kb/2580188 *with workaround****
>
>  to use  System.Configuration.Configuration.GetSection(sectionName).****
>
> ** **
>
> I attach the exception analyze for an better overview. ****
>
> ** **
>
> Is any other case reported or any plan for the workaround integration ?***
> *
>
> ** **
>
> Regards,****
>
> Johannes Dumitru**
>
> ** **
>
> ** **
>