Move to .NET SDK 9.0.300 by idg10 · Pull Request #2208 · dotnet/reactive (original) (raw)
added 29 commits
TBC, but I don't think this is useful to us (since Rx is not intended to be consumed by non-.NET WinRT code) and it's kicking in only because we have types that implement IDisposable.
It's possible that this is only happening because of an SDK bug.
This is attempting to generate code for a scenario we don't support (use of Rx types from non-.NET languages via WinRT). It causes a lot of diagnostic messages, and may also be causing unproductive code bloat.
This mostly entails using collection expression syntax. We were already using it in a lot of places, but with the 9.0 SDK we saw a load of extra diagnostics for this in test projects
Turns out the configuration setting is ignored by everything except pack!
…DotNetCoreCli task seems intent on rewriting quotes in ways I don't want.
…l Debug
Without this change, running dotnet build from the command line fails as it attempts to build the UWP test runner project, something that dotnet build can't actually build.
There were situations in which Scheduling a timed work item in the TaskPoolScheduler would occasionally end up running the work before returning from Schedule. This was not intentional, and occurred due small window in which a Delay task could complete before a continuation was attached to it. (This only seems to have started happening in .NET 9.0.)
#2207 Also I realised there were bugs in the relevant tests: they had Asserts inside the work item callbacks, but those assertions would fire on threads not known to the unit test framework, and nothing in the test code attempted to await the work and rethrow back on the test thread. So I restructured these to move all of the assertions back into the main test bodies.
VS decided after a few minutes idle that it had changed its mind about some diagnoser results, so I had to change some more settings.
Fix typo in ADR
Co-authored-by: Howard van Rooijen howard.vanrooijen@endjin.com
We had a workaround for xunit/xunit#2703 but this has been fixed, so by upgrading we can remove the workaround.
This is good because it turns out the workaround doesn't work if you have a machine with a dev drive user via an alias folder. (Some parts of the build system resolve to the unaliased dev drive path, and so our didn't actually match the thing it's meant to be removing!)
idg10 added a commit that referenced this pull request
Unit tests now run on net9.0 (and continue to run on net8.0, net472, and UWP) Removed .net6.0 and .net7.0 targets from test runner because those runtimes are out of support Removed dependency on MSBuild.SDK.Extras
that may beclosed by this pull request
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})