Skip to content

Move to the .NET 5 SDK#46038

Merged
jaredpar merged 3 commits intodotnet:masterfrom
jaredpar:sdk
Jul 22, 2020
Merged

Move to the .NET 5 SDK#46038
jaredpar merged 3 commits intodotnet:masterfrom
jaredpar:sdk

Conversation

@jaredpar
Copy link
Member

@jaredpar jaredpar commented Jul 16, 2020

This is necessary for us to test features like covariant returns because
we need to be able to target net5.0 in our unit test projects.

Issues encountered in this update:

This is necessary for us to test features like covariant returns because
we need to be able to target `net5.0` in our unit test projects.

Issues encountered in this update:

- WinRT is no longer supported in .NET 5. As a result we no longer multi-target
.NET Core in our WinRT test assembly as well as having to disabling a
few WinRT tests in others.  dotnet/runtime#37672
- Change our Debugger Proxy tests to react to a runtime change
dotnet/runtime@c362923
- Work around .NET5 P6 bug dotnet/sdk#11862
@jaredpar jaredpar marked this pull request as ready for review July 22, 2020 16:58
@jaredpar jaredpar requested review from a team as code owners July 22, 2020 16:58
@jaredpar
Copy link
Member Author

@dotnet/roslyn-infrastructure PTAL

Copy link
Contributor

@sharwell sharwell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There seems to be some inconsistency between references to Preview 6 and Preview 7. I suggested changes to consolidate on Preview 7.

@jaredpar
Copy link
Member Author

@sharwell

There seems to be some inconsistency between references to Preview 6 and Preview 7. I suggested changes to consolidate on Preview 7.

Turns out it hit release just as I was re-prepping this change for review. All my work had been done off of preview 6.

@jaredpar
Copy link
Member Author

@sharwell should be consistent now.

@RikkiGibson
Copy link
Member

Does this need to wait until 16.8-preview1 is publicly released before merging?

@jaredpar
Copy link
Member Author

@RikkiGibson no. The P8 build is the one that has a 16.8 requirement, not P7.

@jaredpar
Copy link
Member Author

The one test failure is TestDefaultDiagnosticProviderRemove which appears to be flaky at the moment. I will file a bug shortly. Merging.

@jaredpar jaredpar merged commit d5fafa1 into dotnet:master Jul 22, 2020
@ghost ghost added this to the Next milestone Jul 22, 2020
@tmat
Copy link
Member

tmat commented Jul 22, 2020

  1. Visual Studio 2019 16.5

Is this still sufficient version?


Refers to: docs/contributing/Building, Debugging, and Testing on Windows.md:18 in e413cc6. [](commit_id = e413cc6, deletion_comment = False)

@tmat
Copy link
Member

tmat commented Jul 22, 2020

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants