dotnet-config
A global tool for managing hierarchical configurations for dotnet tools, using git config format. Usage: dotnet config [options] Location (uses all locations by default) --local use .netconfig.user file --global use global config file --system use system config file --path[=VALUE] use given config file or directory Action --get get value: name [value-regex] --get-all get all values: key [value-regex] --get-regexp get values for regexp: name-regex [value-regex] --set set value: name value [value-regex] --set-all set all matches: name value [value-regex] --add add a new variable: name value --unset remove a variable: name [value-regex] --unset-all remove all matches: name [value-regex] --remove-section remove a section: name --rename-section rename section: old-name new-name -l, --list list all -e, --edit edit the config file in an editor Other --default[=VALUE] with --get, use default value when missing entry --name-only show variable names only --type[=VALUE] value is given this type, can be 'boolean', ' datetime' or 'number' -?, -h, --help Display this help
Install
dotnet add package dotnet-config --version 1.1.0
Install-Package dotnet-config -Version 1.1.0
<PackageReference Include="dotnet-config" Version="1.1.0" />
Frameworks
Dependencies
Adoption guide
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
Compatibility metadata lists 2 target frameworks; confirm the exact target used by your application.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.