Release notes

From versions > [1.3.0] please check it changelog file.

Version 1.3.0

• Added support to .NET 5.0

Version 1.2.4

• Fixed critical bug on UNIX systems where the paths of the appSettings files were not taken properly

Version 1.2.3

• Removed unnecessary appSettings development check due to previous change on .NET Core runtime folder management

Version 1.2.2

• Allowed to use custom AppSetting's param name for appSettings sections: Until this version, was mandatory to have the section to encrypt called "AppSettings", now it is possible to specify the name.

Considerations before:

• The same name should be provided at SetUpSecureConfig method on ConfigureServices (last param) and EncryptSettings (also last param) By default, AppSettings will be the name that the tool will handle.
• Before applying this change, the section name would be renamed, or decrypted first and then renamed. If nothing wants to be changed regarding section name, no change is neccessary, this version has not breaking changes

Please check Home Page for more configuration information

Version 1.2.1

• Configuration extensions now return the Settings files allowing to be used by the rest of the registrations

Version 1.2.0

• NetCore 3.x fix for encryptation mechanism on Program

Version 1.1.0

• NetCore 3.x support

Version 1.0.2

• Allowed to use any kind of private key to encrypt/decrypt the config file

Version 1.0.1

• Fixed critical bug not allowing the tool to find appsettings path different than the default one

Version 1.0.0

• Encryptation / Decryptation of configured sections inside appsettings
• Manage of multiple environment encrypted/decrypted settings
• Installed as NuGet package
• Singleton registration of the configured settings