G
Guest
Hello,
I was looking for specific feature in Configuration but I failed. What I
need, is to set up custom configuration loader - we do not use .NET
Configuration normally for server applications but trying to employ WCF we
need to register into ConfigurationManager (or WebConfigurationManager in
case of web applications) custom provider for sections required by WCF.
The first idea was to add registration of custom settings provider in
startup code. We can pull out the expected sections from our configuration
repository, so it would be transparent for WCF. However, it seems that
Configuration is not flexible enough (in .NET 2.0) as there is no method how
to override the default behavior of ConfigurationManager.AppSettings
property. Any idea?
This seems to be strange as I would expect this must be issue in many
applications, especially enterprise applications. Our scenario is that
logical application is spread into BizTalk, IIS and windows services. It runs
in clustered environment, so the configuration, to be managable, is in a
central place (shared folder available as clustered resource). Nobody wants
to distribute every setting change into every instance of every hosting
service.
Thanks a lot
eXavier
I was looking for specific feature in Configuration but I failed. What I
need, is to set up custom configuration loader - we do not use .NET
Configuration normally for server applications but trying to employ WCF we
need to register into ConfigurationManager (or WebConfigurationManager in
case of web applications) custom provider for sections required by WCF.
The first idea was to add registration of custom settings provider in
startup code. We can pull out the expected sections from our configuration
repository, so it would be transparent for WCF. However, it seems that
Configuration is not flexible enough (in .NET 2.0) as there is no method how
to override the default behavior of ConfigurationManager.AppSettings
property. Any idea?
This seems to be strange as I would expect this must be issue in many
applications, especially enterprise applications. Our scenario is that
logical application is spread into BizTalk, IIS and windows services. It runs
in clustered environment, so the configuration, to be managable, is in a
central place (shared folder available as clustered resource). Nobody wants
to distribute every setting change into every instance of every hosting
service.
Thanks a lot
eXavier