TA.Utils.Logging.Nlog 3.0.0

dotnet add package TA.Utils.Logging.Nlog --version 3.0.0
                    
NuGet\Install-Package TA.Utils.Logging.Nlog -Version 3.0.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="TA.Utils.Logging.Nlog" Version="3.0.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="TA.Utils.Logging.Nlog" Version="3.0.0" />
                    
Directory.Packages.props
<PackageReference Include="TA.Utils.Logging.Nlog" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add TA.Utils.Logging.Nlog --version 3.0.0
                    
#r "nuget: TA.Utils.Logging.Nlog, 3.0.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package TA.Utils.Logging.Nlog@3.0.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=TA.Utils.Logging.Nlog&version=3.0.0
                    
Install as a Cake Addin
#tool nuget:?package=TA.Utils.Logging.Nlog&version=3.0.0
                    
Install as a Cake Tool

NLog Logging Service

This is a logging service implementation that uses NLog as the back-end.

The fluent interface defined in TA.Utils.Diagnostics.IFluentLogBuilder was modeled on the NLog fluent interface, so it is a very natural fit. However, the interface has enough flexibility to adapt to other logging backends without too much trouble.

NLog supports semantic logging. You can use a simple format string like so:

log.Info().Message("Sending data {0}", data).Write();
log.Error().Message("Exception {0} occurred with error code {1}", ex.Message, errorCode).Write();

But this leaves some functionality on the table. Extra rich information can be included like so:

log.Info().Message("Sending data {data}", data).Write();
log.Error()
    .Message("Exception {exception} occurred with error code {error}")
    .Property("exception", ex.Message)
    .Property("error", errorCode)
    .Exception(ex)
    .Write();

When using NLog, you never need to be concerned about output formatting or where the log messages will go. This is all handled by NLog and the NLog.config file in the application directory. There is a lot of flexibility in this approach. As the developer, just concentrate on putting rich information into your log entries.

By default, the log name (source) is set to the file name of the source file where the log entry is created. This is fine for most purposes. This behaviour can be everridden either by specifying the log name along with the level:

log.Debug("Custom Source").Message("Hello log").Write();

or by adding an explicit name entry when building the log entry:

log.Debug().Message("Hello log").LoggerName("Custom Source").Write();
Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
3.0.0 159 6/26/2025
2.8.1 111 3/15/2025
2.8.0 148 7/8/2024
2.6.0 103 3/25/2024
2.5.0 86 3/9/2024
2.3.1 83 1/16/2024
2.3.0 150 11/30/2023
2.2.0 176 10/10/2023
2.1.0 110 9/4/2023
1.3.0 827 9/8/2020
1.1.1 600 7/18/2020
1.1.0 593 7/17/2020