ConfigHelperPro 1.5.0
dotnet add package ConfigHelperPro --version 1.5.0
NuGet\Install-Package ConfigHelperPro -Version 1.5.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="ConfigHelperPro" Version="1.5.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add ConfigHelperPro --version 1.5.0
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: ConfigHelperPro, 1.5.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install ConfigHelperPro as a Cake Addin #addin nuget:?package=ConfigHelperPro&version=1.5.0 // Install ConfigHelperPro as a Cake Tool #tool nuget:?package=ConfigHelperPro&version=1.5.0
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
The Config Helper Pro Library has the ability to manage all your .NET configuration needs. Read/write to the registry, application/web config, and INI files with a single line of code. Everything is 100% managed code.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET Framework | net35 is compatible. net40 is compatible. net403 was computed. net45 is compatible. net451 is compatible. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
GitHub repositories
This package is not used by any popular GitHub repositories.
Kellerman Software announces a minor update to the Config Helper Library. This update fixes a compatibility issue with projects using ClickOnce deployments.