Skip to content

System.Configuration is missing #14427

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
karldodd opened this issue Apr 8, 2015 · 2 comments
Closed

System.Configuration is missing #14427

karldodd opened this issue Apr 8, 2015 · 2 comments
Assignees
Milestone

Comments

@karldodd
Copy link

karldodd commented Apr 8, 2015

Hi corefx team,

If I am right, classes under System.Configuration namespace are missing. I know asp.net 5 introduces some new json-based configuration mechanism but the old xml-based configurations are still widely used. Moving System.Configuraiton to corefx will benefit a lot of legacy code.

Kind regards,
Karl

@holytshirt
Copy link

Hello corefx team, is this namespace coming over, or should we be looking to implement reading from config and custom configuration sections differently?

@Eilon
Copy link
Contributor

Eilon commented Oct 13, 2015

Hi folks, this is Eilon from the ASP.NET team. There are no current plans to bring the System.Configuration types to corefx.

The new Microsoft.Extensions.Configuration is a great alternative way to have structured, layered, testable, DI-friendly configuration data and settings, including many built-in config sources, such as: command line args, environment variables, INI files, JSON files, XML files, and per-machine user secrets.

Though it's not intended as an exact replacement for System.Configuration, it does provide a lightweight, yet powerful way of reading configuration data.

The new library also includes functionality for binding configuration data to strongly-typed POCO objects.

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 1.0.0-rtm milestone Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jan 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants