All notable changes to this project will be documented in this file.
v2.0.0 (2018-10-15)
Miqo.Config has been rewritten with a brand new fluent interface. The library also supports custom file formats for those who want to add support for working with .xml, .ini, .yaml or any other file format.
- Miqo.Config is now a .NET Standard 2.0 library.
ConfigurationManager()
has been marked as deprecated. UseMiqoConfig()
instead.
- Support for custom file formats. There is a very basic example of creating XML files.
- Logging has been reworked.
- Support for saving to and reading from
IO.Streams
.
- Encrypted properties were saved as a hex formatted string. They are now saved as base64 strings. Miqo.Config will still read the old hex formatted properties.
- AES encryption keys were saved as a hex formatted string. They are now saved as base64 strings. Miqo.Config will still read the old hex formatted keys.
- New
.editorconfig
file. - Removed the CreateKeys tools as it's redundant. Use
StringCipher.CreateRandomKey()
instead.
v1.1.2 (2018-08-11)
- add conditional TargetFramework to .csproj (d1b9ecb)
v1.1.1 (2018-07-27)
- Fix README.md with regards to supported versions of .NET (574f3d5)
- Fix NuGet package information with regards to supported versions of .NET (9ff0179)
v1.1.0 (2018-07-26)
- New README.md file
- Restructure project using new .csproj format
- Add Key Creation Tool to the project to help developers create a new private key for their product
- BREAKING: Miqo.Config now runs on .NET Standard 2.0, .NET Core 2.0 and .NET 4.6.1
- BREAKING: Encryption code has been changed. (9ff0179)
The code that handles sensitive information encryption and decryption has been changed. Miqo.Config now uses the Ckode.Encryption library by Steffen Skov for AES encryption and decryption.
Private keys in version 1.0 is not compatible with v1.1. Files that contain encrypted settings from v1.0 will not be decrypted by v1.1.
I apologize for the extra work and frustration this entails for you as a developer. Any such changes in the future will result in a deprecation notice in advance.