XmlHierarchyConfigurator seems like a fairly complex class that was designed to parse a particular file structure without much thought for extensibility (its probably not a good thing to encourage people to use their own slightly different configuration file structure). Take the SetParameter method for example...making that virtual (~250 lines) would allow you to change how parameters are set but my guess is that you'd still need to copy and paste a lot of that code to get your override to perform similiar to the base method.
What parts of XmlHierarchyConfigurator do you want to override? ----- Original Message ---- From: Igor Trofimov <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, December 6, 2006 4:33:56 AM Subject: XmlHierarchyConfigurator Hi, All! I have some private extension for default Hierarchy. And i want to configure it and update it on config-file changes. I can use basic configuration features, but its insufficient. For example, i want to especially parse some children nodes, as it do XmlHierarchyConfigurator. And, i want no ResetConfiguration required to clear my collection properties and fill again from scratch. I can completely write (copy&rewrite) own configurator instead of XmlHierarchyConfigurator, but it is ugly decision, of course - i will lost any compatibility with possible changes of default configuration. What about making XmlHierarchyConfigurator methods virtual?
