We would like to move web.config sections to separate files. Some sections lack configSource attribute and hence not movable: <system.webServer> and some others. Is it possible to somehow intercept and hot-swap the reading process of such configs by framework?
Not sure if OpenExeConfiguration is used when ASP.NET reads such sections, but even if it does, there seems to be no way on changing it's behaviour.
We want an ability to read section content from elsewhere and make it look as if it was read from web.config.