Warning situation at compile. #43
Description
Currently, there is too much warnings happening, due to mainly 2 reasons:
- Others project Nuget being present in the project directly for some reasons (lack of net 6/7 from netcoreserver), no LIBSECURE support yet in the Bouncy Castle nuget, Not NET6/7/8 support in ICSharpZipLib.
One way of getting around the netcore situation is to update the SSFW server with an other API or (watson directly), that solution will be worked on, as this backend is notorious for it's memory usage problems.
- Bump from netcore 3.1 to net 6/7/8 in projects like horizon, where nullable wasn't handled the same way.
It is ensured, that none of those warnings can result in a problem directly, the server stability has been improved massively over time.