Once you have everything configured, then the configuration policies should "just work" by accessing the standard Enterprise Library APIs (container and static facades).
Yes, you still need the local configuration file reference. First the local configuration file is read and then the group policies are applied on top overriding any local configuration. ASP.NET
Configuration and Group Policy, Part 3: Using the Enterprise Library Manageable Configuration Extensions is a good article. It's old but it should still apply for the most part.
My gut reaction would be to stay away from using the ManageableConfigurationSourceImplementation class unless it is absolutely necessary since it is an internal implementation class. You would need to verify that it is being used properly
and also it could change in future releases of Enterprise Library.
Can you use the ManageableConfigurationSource:
IDictionary<string, ConfigurationSectionManageabilityProvider> manageabilityProviders,
And then add a section handler:
var configSource = new ManageableConfigurationSource(configFilePath, manageabilityProviders, true, "MyApp");
configSource.AddSectionChangeHandler(LoggingSettings.SectionName, new ConfigurationChangedEventHandler(
(o, e) =>
var coordinator = o as ConfigurationChangeNotificationCoordinator;
I'm not sure if SourceChanged hooks into the coordinator in this case.
Enterprise Library support engineer