Found 107 packages
The Bugsnag .NET configuration library is used to configure your Bugsnag integration using a Web.config or App.config
Creates objects from IConfiguration and IConfigurationSection objects. A replacement for some of the functionality of Microsoft.Extensions.Configuration.Binder.
Extends the Microsoft.Extensions.Configuration.Binder code to support discriminator based inheritance
Abstractions of key-value pair based configuration. Commonly used types: Microsoft.Extensions.Configuration.IConfiguration Microsoft.Extensions.Configuration.IConfigurationBuilder Microsoft.Extensions.Configuration.IConfigurationProvider Microsoft.Extensions.Configuration.IConfigurationRoot Microsoft.Extensions.Configuration.IConfigurationSection
ConfigurationSection repo for RToggle
Extensions for Microsoft.Extensions.Configuration.Binder that simplifies the process of binding a configuration sub-section to a class, a little bit.
BundleTransformer.ConfigurationIntelliSense adds a IntelliSense support during editing of the `bundleTransformer` configuration section in the `Web.config` file.
Simplifies defining .net configuration sections. Removes the ceremony required to define config sections by providing a mechanism to define your config structure in terms of plain old interfaces.
VTEX library designed to extend custom ConfigurationSection and allow they to reload configuration through defined restore plugin
A custom configuraiton section mainly for logging purpose.
Aerospike plugin for C# DynamicSection project
Determine configuration file section name for an option class and bind the section to the class
Source code package. An extension for getting the distinct section names (top-level keys) for which the given IConfigurationProvider provides configuration data.
Facilitate parsing configuration files from Cisco routers and switches into a document object model (DOM) enabling network administrators and developers to easily read, query, and modify the structured data from Cisco device configurations
An easy way to read custom configuration
Provides a .NET Configuration Section for the EventDay Api Client
This package exists to solve problems with loading the `system.diagnostics` config section under **.NET Core**.
Custom Configuration Section to facilitate Aleph1.DI configuration
The main functions of IoC.Configuration library are: 1) Container agnostic configuration of dependency injection using XML configuration file. The file has section where container can be specified, that will be handling dependency injection resolutions. Currently two popular containers are supported, Ninject and Autofac, via extension libraries IoC.Configuration.Ninject and IoC.Configuration.Autofac, that are available in Nuget.org. The dependency injection container (e.g., Autofac, Ninject) can be easily switched in configuration file. In addition, the configuration file has sections for settings, plugins, startup actions, dynamically generated implementations of interfaces (see autoService elements under iocConfiguration/dependencyInjection/autoGeneratedServices in example configuration files in GitHub test projects in https://github.com/artakhak/IoC.Configuration/tree/master/IoC.Configuration.Tests). 2) Container agnostic configuration of dependency injection in code. The bindings are specified using IoC.Configuration chained methods, however the actual resolutions are done using one of the popular dependency injection containers, Ninject and Autofac, via extension libraries IoC.Configuration.Ninject and IoC.Configuration.Autofac. Note: Use either IoC.Configuration.Ninject 2.0.0 or higher, or IoC.Configuration.Autofac 2.0.0 with IoC.Configuration.Autofac 2.x.x.
A .NET library which allows you to read and write plain-text minimal syntax configuration files. As the name implies, you can have sections and subsections as well.