Fix net462 tests and some async improvements #756
Merged
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.
Background
We noticed that some of the async/await code in the async
BasicRepository
was inconsistent.As part of routine maintenance, I cleaned this up.
In doing so, I discovered that the tests had not been running on the
net462
target for quite some time, due to a bug in the NUnit test runner that occurred when the .NET 7 SDK was present on the host machine.This issue was fixed in September 2022, and upon upgrading the NUnit runner I discovered that a few breakages/incompatibilities had crept into the codebase.
Results
CS4014
,CA1849
,CA2012
,CA2016
which help ensure we are handling async/await correctly.LangVersion
to 8 forOctopus.Client.csproj
ConfigureAwait(false)
andasync
methods inBasicRepository.cs
,MixedScopeBaseRepository.cs
andUserInvitesRepository