nanoFramework.Logging 1.1.120

Prefix Reserved
dotnet add package nanoFramework.Logging --version 1.1.120                
NuGet\Install-Package nanoFramework.Logging -Version 1.1.120                
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="nanoFramework.Logging" Version="1.1.120" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add nanoFramework.Logging --version 1.1.120                
#r "nuget: nanoFramework.Logging, 1.1.120"                
#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.
// Install nanoFramework.Logging as a Cake Addin
#addin nuget:?package=nanoFramework.Logging&version=1.1.120

// Install nanoFramework.Logging as a Cake Tool
#tool nuget:?package=nanoFramework.Logging&version=1.1.120                

Quality Gate Status Reliability Rating License NuGet #yourfirstpr Discord

nanoFramework logo


Welcome to the .NET nanoFramework nanoFramework.Logging Library repository

Build status

Component Build Status NuGet Package
nanoFramework.Logging Build Status NuGet
nanoFramework.Logging.Serial Build Status NuGet
nanoFramework.Logging.Stream Build Status NuGet
nanoFramework.Logging.Syslog Build Status NuGet

Feedback and documentation

For documentation, providing feedback, issues and finding out how to contribute please refer to the Home repo.

Join our Discord community here.

Credits

The list of contributors to this project can be found at CONTRIBUTORS.

License

The nanoFramework Class Libraries are licensed under the MIT license.

Usage

In your class, make sure you have a global ILogger declared and in your constructor that you call _logger = this.GetCurrentClassLogger();

using Microsoft.Extensions.Logging;
using nanoFramework.Logging;
using System;

namespace UnitTestDebugLogging
{
    internal class MyTestComponent
    {
        private ILogger _logger;

        public MyTestComponent()
        {
            _logger = this.GetCurrentClassLogger();
        }

        public void DoSomeLogging()
        {
            _logger.LogInformation("An informative message");
            _logger.LogError("An error situation");
            _logger.LogWarning(new Exception("Something is not supported"), "With exception context");
        }
    }
}

In your main code, you'll need to create a logger:

LogDispatcher.LoggerFactory = new DebugLoggerFactory();
// Then you can create your object and the logging will happen
MyTestComponent test = new MyTestComponent();
test.DoSomeLogging();

You can have 3 different types of logger: Debug, Serial and Stream.

Debug logger

As presented previously, you can use the Factory pattern:

LogDispatcher.LoggerFactory = new DebugLoggerFactory();
// Then you can create your object and the logging will happen
MyTestComponent test = new MyTestComponent();
test.DoSomeLogging();

You can as well directly create a DebugLogger:

DebugLogger _logger;
_logger = new DebugLogger("test");
_logger.MinLogLevel = LogLevel.Trace; 
_logger.LogTrace("This is a trace");

Serial logger

You can use the Factory pattern:

LogDispatcher.LoggerFactory = new SerialLoggerFactory("COM6");
// Then you can create your object and the logging will happen
MyTestComponent test = new MyTestComponent();
test.DoSomeLogging();

Note that you can adjust the baud speed and all other elements.

Or directly using a SerialLogger:

SerialPort _serial;
_serial = new SerialPort("COM6", 115200);
SerialLogger _logger = new SerialLogger(ref _serial);
_logger.MinLogLevel = LogLevel.Trace; 
_logger.LogTrace("This is a trace");

Important: make sure to refer to the documentation of your board to understand how to properly setup the serial port. The tests include an example with an ESP32.

Stream logger

Similar as for the others, you can either use a FileStream or a Stream in the LoggerFactory:

MemoryStream memoryStream = new MemoryStream();
LogDispatcher.LoggerFactory = new StreamLoggerFactory(memoryStream);
MyTestComponent test = new MyTestComponent();
test.DoSomeLogging();

And you can as well use it directly:

var _stream = new FileStream("D:\\mylog.txt", FileMode.Open, FileAccess.ReadWrite);
StreamLogger _logger = new StreamLogger(_stream);
_logger.MinLogLevel = LogLevel.Trace; 
_logger.LogTrace("This is a trace");

Important: please refer to the documentation for USB and SD Card reader to make sure they are properly setup before trying to setup the logger.

Create your own logger

You can create your own logger using the ILogger and ILoggerFactory interfaces. The DebugLogger is the simplest one.

The Log extensions

Different Log extensions are at your disposal to help you log the way you like. You can simply log a string or having parameters as well as exception and EventId:

_logger.LogTrace("TRACE {0} {1}", new object[] { "param 1", 42 });
_logger.LogDebug("DEBUG {0} {1}", new object[] { "param 1", 42 });
_logger.LogInformation("INFORMATION and nothing else");
_logger.LogWarning("WARNING {0} {1}", new object[] { "param 1", 42 });
_logger.LogError(new Exception("Big problem"), "ERROR {0} {1}", new object[] { "param 1", 42 });
_logger.LogCritical(42, new Exception("Insane problem"), "CRITICAL {0} {1}", new object[] { "param 1", 42 });

Note that all log level extensions have a minimum of string logging upo to EventId, string, parameters and exception. You are responsible to format properly the string when there are parameters.

Log level

You can adjust the log level in all the predefined logger. For example:

DebugLogger _logger;
_logger = new DebugLogger("test");
_logger.MinLogLevel = LogLevel.Trace;
_logger.LogTrace("This will be displayed");
_logger.LogCritical("Critical message will be displayed");
_logger.MinLogLevel = LogLevel.Critical;
_logger.LogTrace("This won't be displayed, only critical will be");
_logger.LogCritical("Critical message will be displayed");

Create your own formatting

You can use a custom formatter which will give you the name of the logger, the log level, the event ID, the message itself and a potential exception. The function definition should follow the following pattern:

public interface IMessageFormatter
{     
    string MessageFormatter(string className, LogLevel logLevel, EventId eventId, string state, Exception exception);
}

Important: this function will be called directly, without instantiating the class it is part of. So make sure either this function is a static, either it's part of the class using the logger. The static option always works. The interface is given for convenience and to give the format.

To setup the formatting, just use the following line. The type of the class containing the function and the exact name of the function are required.

LoggerExtensions.MessageFormatter = typeof(MyFormatter).GetType().GetMethod("MessageFormatterStatic");

public class MyFormatter
{        
    public string MessageFormatterStatic(string className, LogLevel logLevel, EventId eventId, string state, Exception exception)
    {
        string logstr = string.Empty;
        switch (logLevel)
        {
            case LogLevel.Trace:
                logstr = "TRACE: ";
                break;
            case LogLevel.Debug:
                logstr = "I love debug: ";
                break;
            case LogLevel.Warning:
                logstr = "WARNING: ";
                break;
            case LogLevel.Error:
                logstr = "ERROR: ";
                break;
            case LogLevel.Critical:
                logstr = "CRITICAL:";
                break;
            case LogLevel.None:
            case LogLevel.Information:
            default:
                break;
        }

        string eventstr = eventId.Id != 0 ? $" Event ID: {eventId}, " : string.Empty;
        string msg = $"[{className}] {eventstr}{logstr} {state}";
        if (exception != null)
        {
            msg += $" {exception}";
        }

        return msg;
    }
}

You are free to use anything you'd like and format as you like the message.

Note: It is not necessary to add a \r\n at the end, this is done by each logger.

Code of Conduct

This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behaviour in our community. For more information see the .NET Foundation Code of Conduct.

.NET Foundation

This project is supported by the .NET Foundation.

Product Compatible and additional computed target framework versions.
.NET Framework net is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (16)

Showing the top 5 NuGet packages that depend on nanoFramework.Logging:

Package Downloads
nanoFramework.Logging.Stream

This package includes the nanoFramework.Logging.Stream assembly (Stream Logging only) for .NET nanoFramework C# projects. There is also a package with the Serial Logger only and another with the basic Debug Logger.

nanoFramework.Logging.Serial

This package includes the nanoFramework.Logging.Serial assembly (Serial Logging only) for .NET nanoFramework C# projects. There is also a package with the Stream Logging only and another with the basic Debug Logging.

nanoFramework.Iot.Device.Mfrc522

This package includes the .NET IoT Core binding Iot.Device.Mfrc522 for .NET nanoFramework C# projects.

nanoFramework.Iot.Device.Pn532

This package includes the .NET IoT Core binding Iot.Device.Pn532 for .NET nanoFramework C# projects.

nanoFramework.Iot.Device.Pn5180

This package includes the .NET IoT Core binding Iot.Device.Pn5180 for .NET nanoFramework C# projects.

GitHub repositories (2)

Showing the top 2 popular GitHub repositories that depend on nanoFramework.Logging:

Repository Stars
nanoframework/Samples
🍬 Code samples from the nanoFramework team used in testing, proof of concepts and other explorational endeavours
nanoframework/nanoFramework.IoT.Device
📦 This repo includes .NET nanoFramework implementations for various sensors, chips, displays, hats and drivers
Version Downloads Last updated
1.1.120 1,181 12/6/2024
1.1.113 2,728 9/30/2024
1.1.108 4,962 8/1/2024
1.1.107 924 7/23/2024
1.1.100 5,254 5/15/2024
1.1.98 527 5/13/2024
1.1.96 759 5/10/2024
1.1.94 2,635 4/10/2024
1.1.92 449 4/9/2024
1.1.90 239 4/8/2024
1.1.88 915 4/4/2024
1.1.86 450 4/3/2024
1.1.84 264 4/3/2024
1.1.81 4,122 2/1/2024
1.1.79 1,105 1/26/2024
1.1.76 6,007 11/16/2023
1.1.74 2,606 11/10/2023
1.1.63 19,164 1/4/2023
1.1.60 1,965 12/28/2022
1.1.58 1,041 12/28/2022
1.1.47 4,035 10/28/2022
1.1.45 1,462 10/26/2022
1.1.43 1,143 10/26/2022
1.1.41 2,341 10/25/2022
1.1.39 1,187 10/25/2022
1.1.37 1,487 10/24/2022
1.1.35 1,216 10/24/2022
1.1.33 1,261 10/24/2022
1.1.31 1,474 10/23/2022
1.1.29 1,215 10/23/2022
1.1.27 2,035 10/22/2022
1.1.25 3,442 10/10/2022
1.1.23 2,701 10/7/2022
1.1.19 2,759 9/22/2022
1.1.17 2,400 9/16/2022
1.1.15 1,323 9/15/2022
1.1.13 1,336 9/15/2022
1.1.9 1,377 9/15/2022
1.1.7 1,321 9/15/2022
1.1.2 5,512 8/5/2022
1.0.1.29 6,473 6/17/2022
1.0.1.27 2,225 6/16/2022
1.0.1.25 2,161 6/14/2022
1.0.1.23 2,124 6/13/2022
1.0.1.21 1,321 6/9/2022
1.0.1.19 1,313 6/8/2022
1.0.1.15 2,343 5/27/2022
1.0.1.13 2,796 5/19/2022
1.0.1.12 2,260 5/4/2022
1.0.1 5,840 3/28/2022
1.0.1-preview.32 143 3/28/2022
1.0.1-preview.31 129 3/28/2022
1.0.1-preview.30 136 3/28/2022
1.0.1-preview.28 210 3/18/2022
1.0.1-preview.27 136 3/17/2022
1.0.1-preview.26 144 3/15/2022
1.0.1-preview.25 155 3/14/2022
1.0.1-preview.24 148 3/11/2022
1.0.1-preview.23 208 2/25/2022
1.0.1-preview.21 213 2/17/2022
1.0.1-preview.19 175 2/11/2022
1.0.1-preview.18 166 2/8/2022
1.0.1-preview.17 165 2/4/2022
1.0.1-preview.16 188 1/28/2022
1.0.1-preview.15 171 1/28/2022
1.0.1-preview.14 177 1/28/2022
1.0.1-preview.13 176 1/27/2022
1.0.1-preview.12 152 1/26/2022
1.0.1-preview.11 142 1/25/2022
1.0.1-preview.10 160 1/25/2022
1.0.1-preview.9 169 1/21/2022
1.0.1-preview.8 151 1/21/2022
1.0.1-preview.6 196 1/14/2022
1.0.1-preview.4 206 1/4/2022
1.0.1-preview.3 154 12/29/2021
1.0.0 1,633 12/5/2021
1.0.0-preview.142 172 12/5/2021
1.0.0-preview.141 160 12/5/2021
1.0.0-preview.137 296 10/19/2021
1.0.0-preview.135 213 10/18/2021
1.0.0-preview.133 362 10/15/2021
1.0.0-preview.131 302 9/30/2021
1.0.0-preview.129 200 9/27/2021
1.0.0-preview.127 274 9/26/2021
1.0.0-preview.122 920 7/18/2021
1.0.0-preview.120 262 7/17/2021
1.0.0-preview.118 571 7/16/2021
1.0.0-preview.116 187 7/15/2021
1.0.0-preview.114 208 7/14/2021
1.0.0-preview.110 271 6/29/2021
1.0.0-preview.108 271 6/27/2021
1.0.0-preview.106 179 6/21/2021
1.0.0-preview.104 207 6/20/2021
1.0.0-preview.102 163 6/19/2021
1.0.0-preview.100 171 6/19/2021
1.0.0-preview.98 228 6/9/2021
1.0.0-preview.96 192 6/8/2021
1.0.0-preview.94 180 6/7/2021
1.0.0-preview.92 203 6/7/2021
1.0.0-preview.90 183 6/6/2021
1.0.0-preview.88 278 6/5/2021
1.0.0-preview.86 170 6/4/2021
1.0.0-preview.84 153 6/3/2021
1.0.0-preview.82 200 6/3/2021
1.0.0-preview.80 179 6/2/2021
1.0.0-preview.78 205 6/1/2021
1.0.0-preview.76 199 5/31/2021
1.0.0-preview.74 208 5/31/2021
1.0.0-preview.72 200 5/31/2021
1.0.0-preview.70 235 5/30/2021
1.0.0-preview.68 205 5/30/2021
1.0.0-preview.66 173 5/29/2021
1.0.0-preview.64 175 5/27/2021
1.0.0-preview.62 179 5/26/2021
1.0.0-preview.60 317 5/25/2021
1.0.0-preview.58 306 5/23/2021
1.0.0-preview.56 196 5/22/2021
1.0.0-preview.54 225 5/21/2021
1.0.0-preview.52 236 5/20/2021
1.0.0-preview.50 167 5/19/2021
1.0.0-preview.48 196 5/19/2021
1.0.0-preview.46 284 5/16/2021
1.0.0-preview.44 182 5/15/2021
1.0.0-preview.42 176 5/14/2021
1.0.0-preview.40 181 5/13/2021
1.0.0-preview.38 171 5/12/2021
1.0.0-preview.36 231 5/7/2021
1.0.0-preview.34 227 5/6/2021
1.0.0-preview.32 175 5/5/2021
1.0.0-preview.30 178 5/4/2021
1.0.0-preview.28 169 5/4/2021
1.0.0-preview.26 186 4/23/2021
1.0.0-preview.25 175 4/12/2021
1.0.0-preview.24 185 4/10/2021
1.0.0-preview.21 690 4/9/2021
1.0.0-preview.19 184 4/9/2021
1.0.0-preview.17 202 4/8/2021
1.0.0-preview.14 200 4/8/2021
1.0.0-preview.13 199 4/8/2021