rgLogger 1.3.0

There is a newer version of this package available.
See the version list below for details.
dotnet add package rgLogger --version 1.3.0                
NuGet\Install-Package rgLogger -Version 1.3.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="rgLogger" Version="1.3.0" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add rgLogger --version 1.3.0                
#r "nuget: rgLogger, 1.3.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.
// Install rgLogger as a Cake Addin
#addin nuget:?package=rgLogger&version=1.3.0

// Install rgLogger as a Cake Tool
#tool nuget:?package=rgLogger&version=1.3.0                

A simple, light-weight .NET logging library capable of easily writing to the console, files, email, which is also simple to extend for additional functionality.

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.

This package has no dependencies.

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
1.3.4 1,196 4/6/2016
1.3.3.3 982 3/29/2016
1.3.3 1,267 3/29/2016
1.3.2 1,365 3/11/2016
1.3.1 972 2/10/2016
1.3.0 1,295 1/31/2016

Version 1.3.0 includes many breaking changes. A lot of the code didn't align with the official C# Coding Conventions document so I ran the solution through StyleCop and fixed issues with the names of public properties and methods.

Apologies to anyone that installed the previous 1.2 version as you may need to change a lot of your code. Going forward we will stick to the coding conventions standards and this won't be an issue again.