cdmdotnet.Performance
1.0.4.7
Prefix Reserved
See the version list below for details.
dotnet add package cdmdotnet.Performance --version 1.0.4.7
NuGet\Install-Package cdmdotnet.Performance -Version 1.0.4.7
<PackageReference Include="cdmdotnet.Performance" Version="1.0.4.7" />
paket add cdmdotnet.Performance --version 1.0.4.7
#r "nuget: cdmdotnet.Performance, 1.0.4.7"
// Install cdmdotnet.Performance as a Cake Addin #addin nuget:?package=cdmdotnet.Performance&version=1.0.4.7 // Install cdmdotnet.Performance as a Cake Tool #tool nuget:?package=cdmdotnet.Performance&version=1.0.4.7
cdmdotnet.Performance
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net40 is compatible. net403 was computed. net45 was computed. net451 was computed. 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. |
This package has no dependencies.
NuGet packages (2)
Showing the top 2 NuGet packages that depend on cdmdotnet.Performance:
Package | Downloads |
---|---|
cdmdotnet.Logging
This logging library makes large use of enterprise correlation. In a lot of applications that incorporate various small and large services, it is often important to correlate events that happen across these services. It gives us a business workflow view of the various events that happen in the application, its components and services. This library provide operation and activity ID management and propagation. The main difference with this library over other is that you can configure each type of log separately. You can enable fatal, error, warning, debugging, informational, progress and sensitive data logging all independently of each other. This is more flexible than the concept of minimum level logging, such as that in log4net or serilog e.g. enabling one warning in this libraries will enable error and fatal logging as well. This library allows you to set those settings independently of each other. The SqlLogger maps AdditionalData to table columns, where the key of the dictionary entry is the column name and the value is serialised to JSON as the column value. MetaData is serialised to a single JSON value stored in the MetaData column. This means you can store data such as a User ID or Job ID in a separate column so you can filter more efficiently with indexes and partitions. TraceLogger and ConsoleLogger both seralise and format all information into a single string. The MultiLogger allows you to configure several different loggers to be used at once with different settings for each logger. Usage is in the form of: static void Main() { ICorrelationIdHelper correlationIdHelper = new WebCorrelationIdHelper(); // This value will be set automatically to all logs within this thread... so long as System.Threading.Tasks.Task.Factory.StartNew is used. correlationIdHelper.SetCorrelationId(Guid.NewGuid()); DoSyncWork(); DoAsyncWork(); } static void DoSyncWork() { ILogger logger = new SqlLogger(); logger.LogDebug("Some technical debugging details."); } static void DoAsyncWork() { System.Threading.Tasks.Task.Factory.StartNew(() => { ILogger logger = new ConsoleLogger(); logger.LogInfo("An informative message."); }); } This package installs cdmdotnet.Logging.dll with includes core logging functionality. Other packages depend on cdmdotnet.Logging for specific implementations. |
|
cdmdotnet.Performance.Web
cdmdotnet.Performance.Web |
GitHub repositories
This package is not used by any popular GitHub repositories.