System.Diagnostics.TraceSource 4.3.0
Provides classes that help you trace the execution of your code. Developers should prefer the classes in the ETW-based System.Diagnostics.Tracing package.
Commonly Used Types:
System.Diagnostics.TraceListener
System.Diagnostics.TraceLevel
System.Diagnostics.TraceSource
System.Diagnostics.TraceEventType
System.Diagnostics.DefaultTraceListener
System.Diagnostics.Trace
When using NuGet 3.x this package requires at least version 3.4.
Showing the top 20 packages that depend on System.Diagnostics.TraceSource.
| Packages | Downloads |
|---|---|
|
Castle.Core
Castle Core, including DynamicProxy, Logging Abstractions and DictionaryAdapter
|
36 |
|
DnsClient
DnsClient.NET is a simple yet very powerful and high performance open source library for the .NET Framework to do DNS lookups
|
32 |
|
Microsoft.Build
This package contains the Microsoft.Build assembly which is used to create, edit, and evaluate MSBuild projects.
|
28 |
|
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
|
27 |
|
Microsoft.Build
This package contains the Microsoft.Build assembly which is used to create, edit, and evaluate MSBuild projects.
|
27 |
|
Microsoft.Build
This package contains the Microsoft.Build assembly which is used to create, edit, and evaluation MSBuild projects.
|
27 |
|
Castle.Core
Castle Core, including DynamicProxy, Logging Abstractions and DictionaryAdapter
|
26 |
|
Microsoft.TestPlatform.ObjectModel
The Microsoft Test Platform Object Model.
|
26 |
|
Microsoft.Build.Tasks.Core
This package contains the Microsoft.Build.Tasks.Core assembly which implements the commonly used tasks of MSBuild.
|
26 |
|
Serilog
Simple .NET logging with fully-structured events
|
26 |
|
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
|
25 |
|
Microsoft.Build
This package contains the Microsoft.Build assembly which is used to create, edit, and evaluation MSBuild projects.
|
25 |
|
Microsoft.Build
This package contains the Microsoft.Build assembly which is used to create, edit, and evaluate MSBuild projects.
|
25 |
|
Microsoft.Build.Tasks.Core
This package contains the Microsoft.Build.Tasks.Core assembly which implements the commonly used tasks of MSBuild.
|
25 |
|
Serilog
Simple .NET logging with fully-structured events
|
25 |
|
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
|
24 |
https://go.microsoft.com/fwlink/?LinkID=799421
MonoAndroid 1.0
- No dependencies.
Xamarin.WatchOS 1.0
- No dependencies.
Xamarin.TVOS 1.0
- No dependencies.
Xamarin.Mac 2.0
- No dependencies.
Xamarin.iOS 1.0
- No dependencies.
.NET Standard 1.3
- System.Runtime.Extensions (>= 4.3.0)
- System.Runtime (>= 4.3.0)
- System.Resources.ResourceManager (>= 4.3.0)
- System.Threading (>= 4.3.0)
- System.Diagnostics.Debug (>= 4.3.0)
- System.Collections (>= 4.3.0)
- runtime.native.System (>= 4.3.0)
- Microsoft.NETCore.Platforms (>= 1.1.0)
- System.Globalization (>= 4.3.0)
.NET Framework 4.6
- No dependencies.
MonoTouch 1.0
- No dependencies.
| Version | Downloads | Last updated |
|---|---|---|
| 4.3.0 | 32 | 7/2/2023 |
| 4.3.0-preview1-24530-04 | 23 | 7/2/2023 |
| 4.0.0 | 25 | 4/12/2022 |
| 4.0.0-rc2-24027 | 22 | 7/2/2023 |
| 4.0.0-beta-23516 | 26 | 7/2/2023 |
| 4.0.0-beta-23409 | 23 | 7/2/2023 |
| 4.0.0-beta-23225 | 21 | 7/2/2023 |
| 4.0.0-beta-23123 | 23 | 7/2/2023 |
| 4.0.0-beta-23109 | 26 | 7/2/2023 |
| 4.0.0-beta-23019 | 21 | 7/2/2023 |
| 4.0.0-beta-22816 | 19 | 7/2/2023 |
| 4.0.0-beta-22605 | 25 | 7/2/2023 |
| 4.0.0-beta-22416 | 23 | 7/2/2023 |
| 4.0.0-beta-22231 | 25 | 7/2/2023 |