XElement and XDocument both inherit XContainer, and so both produce compiling code when passed as an argument to the InMemoryConfigurationSource.SetConfigurationXml method. This flexibility is not reflected in the section retrieval code, however, as each concrete type has different starting node levels in Linq-to-XML queries, but InMemoryConfigurationSource only has one strategy for dealing with its XContainer; that strategy is only valid for XElement instances. Either some form of type-sensitive solution should be implemented, or the XContainer parameter should be changed to one or the other (XDocument or XElement).
XElementandXDocumentboth inheritXContainer, and so both produce compiling code when passed as an argument to theInMemoryConfigurationSource.SetConfigurationXmlmethod. This flexibility is not reflected in the section retrieval code, however, as each concrete type has different starting node levels in Linq-to-XML queries, butInMemoryConfigurationSourceonly has one strategy for dealing with itsXContainer; that strategy is only valid forXElementinstances. Either some form of type-sensitive solution should be implemented, or theXContainerparameter should be changed to one or the other (XDocumentorXElement).