System.Configuration.ConfigurationManager 7.0.0-preview.5.22301.12
Provides types that support using configuration files.
Commonly Used Types:
System.Configuration.Configuration
System.Configuration.ConfigurationManager
Showing the top 20 packages that depend on System.Configuration.ConfigurationManager.
| Packages | Downloads |
|---|---|
|
log4net
log4net is a tool to help the programmer output log statements to a variety of output targets.
In case of problems with an application, it is helpful to enable logging so that the problem
can be located. With log4net it is possible to enable logging at runtime without modifying the
application binary. The log4net package is designed so that log statements can remain in
shipped code without incurring a high performance cost. It follows that the speed of logging
(or rather not logging) is crucial.
At the same time, log output can be so voluminous that it quickly becomes overwhelming.
One of the distinctive features of log4net is the notion of hierarchical loggers.
Using these loggers it is possible to selectively control which log statements are output
at arbitrary granularity.
log4net is designed with two distinct goals in mind: speed and flexibility
|
1 |
|
Microsoft.Build
This package contains the Microsoft.Build assembly which is used to create, edit, and evaluate MSBuild projects.
|
1 |
|
EntityFramework
Entity Framework 6 (EF6) is a tried and tested object-relational mapper for .NET with many years of feature development and stabilization.
|
0 |
|
FluentAssertions
A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or
BDD-style unit tests. Targets .NET Framework 4.5 and 4.7, as well as .NET Core 2.0, .NET Standard 1.3, 1.6 and 2.0.
Supports the unit test frameworks MSTest, MSTest2, Gallio, NUnit, XUnit, MBUnit, MSpec, and NSpec.
|
0 |
|
log4net
log4net is a tool to help the programmer output log statements to a variety of output targets.
In case of problems with an application, it is helpful to enable logging so that the problem
can be located. With log4net it is possible to enable logging at runtime without modifying the
application binary. The log4net package is designed so that log statements can remain in
shipped code without incurring a high performance cost. It follows that the speed of logging
(or rather not logging) is crucial.
At the same time, log output can be so voluminous that it quickly becomes overwhelming.
One of the distinctive features of log4net is the notion of hierarchical loggers.
Using these loggers it is possible to selectively control which log statements are output
at arbitrary granularity.
log4net is designed with two distinct goals in mind: speed and flexibility
|
0 |
|
System.Diagnostics.PerformanceCounter
Provides the System.Diagnostics.PerformanceCounter class, which allows access to Windows performance counters.
Commonly Used Types:
System.Diagnostics.PerformanceCounter
When using NuGet 3.x this package requires at least version 3.4.
|
0 |
|
System.Diagnostics.PerformanceCounter
Provides the System.Diagnostics.PerformanceCounter class, which allows access to Windows performance counters.
Commonly Used Types:
System.Diagnostics.PerformanceCounter
|
0 |
.NET Framework 4.6.2
- System.Security.Permissions (>= 7.0.0-preview.5.22301.12)
.NET 6.0
- System.Security.Cryptography.ProtectedData (>= 7.0.0-preview.5.22301.12)
- System.Security.Permissions (>= 7.0.0-preview.5.22301.12)
.NET 7.0
- System.Security.Cryptography.ProtectedData (>= 7.0.0-preview.5.22301.12)
- System.Security.Permissions (>= 7.0.0-preview.5.22301.12)
.NET Standard 2.0
- System.Security.Cryptography.ProtectedData (>= 7.0.0-preview.5.22301.12)
- System.Security.Permissions (>= 7.0.0-preview.5.22301.12)