Experiment: Separate out the System.Configuration.ConfigurationManage… #234
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…r support
refs #171
As mentioned in #171, an experiment into moving the System.Configuration.ConfigurationManager code into its own assembly, so the main assembly doesn't have a depdency on ConfigurationManager.
This is just an experiment into moving the code out, but keeping the same API (except with it not trying to read appsettings by default any more) - not an experiment into the best API for splitting things.
So - leaving this here in case the idea is considered interesting for a future major version bump with breaking changes.