search

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.

pkg

Limited.MicroService

Package Description

v0.1.3

↙ 21.3K / total

pkg

liesauer.LimitedConcurrencyLevelTaskScheduler.NETStandard

LimitedConcurrencyLevelTaskScheduler for NETStandard

v1.0.1

↙ 17.8K / total

pkg

NotLimited.Framework.Logging

Logging helpers.

v1.1.12

↙ 11.9K / total

pkg

AzureSignTool

Azure Sign Tool is similar to signtool in the Windows SDK, with the major difference being that it uses Azure Key Vault for performing the signing process. The usage is like signtool, except with a limited set of options for signing and options for authenticating to Azure Key Vault.

v7.0.1

↙ 9.8M / total

azuresigntoolazurekeyvaultcodesign

pkg

NotLimited.NamedPipeWrapper

Async named pipe wrapper with structured message support.

v1.0.7

↙ 7.1K / total

pkg

Limited.Gateway

Package Description

v0.1.0

↙ 3.3K / total

pkg

TestingContextLimitedInterface

Testing Context is a tool for advanced data search. Primarily designed for behaviour testing using SpecFlow. https://github.com/repinvv/TestingContext

v3.0.4

↙ 5.0K / total

pkg

Finbourne.EdpLusidSdk

LUSID SDK for EDP

v0.11.6260

↙ 3.6M / total

WinSCP

The WinSCP .NET assembly is a .NET wrapper around WinSCP’s scripting interface that allows your code to connect to a remote machine and manipulate remote files over SFTP, FTP, WebDAV, S3 and SCP sessions. The library is primarily intended for advanced automation tasks on Microsoft Windows that require conditional processing, loops or other control structures for which the basic scripting interface is too limited. The library is not a general purpose file transfer library. It particularly has a limited support for an interactive processing, and as such it is not well suited for use in GUI applications. For the same reason it is also difficult to use the assembly within a restricted environment like a web server, that limits or even restricts execution of external processes. For documentation and examples of use, see project website. The NuGet package includes the assembly itself and a required WinSCP executable. When installed, it adds the assembly as reference to your project and sets up WinSCP executable to be copied to project output directory, so that it can be found on run-time.

v6.5.5

↙ 16.0M / total

winscpsftpftpftpswebdav