Breaking changes

Converting the library to NetStandard 1.1, and making it even more portable, we have introduced 3 breaking changes:

• Only direct configuration set up is allowed
• .Net Framework versions prior 4.5 are not supported anymore
• Entry point class name has been changed

Configuration
In our journey to support new platforms, we standardized the configuration settings approach.
Previously, if you were using BugGuardian in Web, Console, or WinForm applications, you can save your configuration in the web.config / App.config files.
BugGuardian 2.0 doesn't support anymore this approach; it requires that the configuration is set-up excplicity.
Take a look at the Configuration settings section for more details.

.Net Framework Versions
We had to make a choice whether to continue having multiple libraries for different platforms or moving to support NetStandard. We eventually came up with the second option, so now the library targets NetStandard 1.1.

As result, BugGuardian 2.0+ doesn't support anymore applications written with the .Net Framework 4.0 and above. If you still need to target those legacy applications, you can still use the version 1.3 of the library (Nuget, Sources)

Class name change
To make clear that this version is introducing some breaking changes, we have also changed the base class name and its interface from Creator and ICreator to BugGuardianManager and IBugGuardianManager respectively.