Fully move to .net core 3.0 exclusive support

[TonyLo1]

.Net core 3.0 now has support for Winforms and WPF so the UI projects can be ported. A single project platform will be easier to maintain.

[TonyLo1]

For clarification: UI apps will only run on windows at this point but the server build can be consolidated into a single solution file.

[patham9]

The UI only works on Windows, so it's not worth it, you would also loose the configuration ability for your monster machine .NET currently offers.
Maintainence shouldn't be an issue as long as you don't accidentally change the dotnetcore project files again (they don't need to be touched). Additionally I need to stay with dotnetcore 2.2 for now if you want me to be involved, v3 still has serious portability issues.

[patham9]

Best practice would not be to move to new version for new versions sake. Instead it should be configured to compile with >=2.2 so that it will build with 2.2 and 3.0 both (as there is no dependency that would require v3 in ALANN). For GUI: Microsoft won't build cross platform GUI frameworks for core in forseeable future, if you want a GUI that works on dotnetcore in general and also runs on .NET consider using Avalonia.

[TonyLo1]

There is no rush for this. The goal was to move to a single solution file to avoid issues with messed up project files. Updating to the latest version of paket may have resolved the issues with the project file corruption but not certain at this stage. If you need .net core v2.2 then we can stay on this for now.

[patham9]

I see, makes sense. Should also work with a >=2.2 config though hm. To avoid corruption of config file you can also update .gitignore to exclude the dotnetcore files, this way they won't change in the repo.

[TonyLo1]

Can't use .gitignore in this case as the project files need to be updated when files are added