Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #830 and also fixes #511
This runs the tests on .NET 5.0, where available. I thought this was important to at least test on .NET 5.0, as it's a platform I suspect a large number of our users will shortly be running on. I haven't yet seen any reason to add a .NET 5.0 build though - so this instead runs tests for the .NET Core 3.1 Engine/Console on .NET 5.0. I also didn't see a need to add a requirement for users to have .NET 5.0 installed to contribute, so if unavailable, the default is to provide a warning - assuming the tests will be run on all platforms in CI instead.
It also improves the CI's handling of .NET Core platforms, as per #511. The new behaviour:
One day I hope the Engine itself will do all this boilerplate stuff for us...we'll get there! 😄