-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Breaking change] Removal of built-in WinRT support in .NET 5.0 #37672
Labels
area-System.Runtime.InteropServices
breaking-change
Issue or PR that represents a breaking API or functional change over a prerelease.
Milestone
Comments
AaronRobinsonMSFT
added
area-System.Runtime.InteropServices
breaking-change
Issue or PR that represents a breaking API or functional change over a prerelease.
labels
Jun 9, 2020
Dotnet-GitSync-Bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Jun 9, 2020
AaronRobinsonMSFT
removed
the
untriaged
New issue has not been triaged by the area owner
label
Jun 9, 2020
How can I upgrade my .NET Framework 4.x and .NET Core 3.1 VB apps to .NET 5 after this breaking change? Many of them are using WinRT APIs to send toast notifications, share files or save settings. |
@Nukepayload2 You're supposed to use C#/WinRT for that. Have you tried it? |
@Nukepayload2 there are recommended next steps linked above in dotnet/docs#18875. |
This was referenced Jun 12, 2020
jaredpar
added a commit
to jaredpar/roslyn
that referenced
this issue
Jul 22, 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: - 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
added a commit
to dotnet/roslyn
that referenced
this issue
Jul 22, 2020
* Move to the .NET 5 SDK 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
This was referenced Jul 23, 2020
This was referenced Dec 5, 2020
ghost
locked as resolved and limited conversation to collaborators
Dec 8, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-System.Runtime.InteropServices
breaking-change
Issue or PR that represents a breaking API or functional change over a prerelease.
[Breaking change] Removal of built-in WinRT support in .NET 5.0
With the work to provide sustainable and long term support for WinRT consumption in .NET, the built-in support has been removed. This is a high impact change to all existing libraries and application that rely on the built-in WinRT support.
The replacement for built-in WinRT support is the C#/WinRT tool chain.
For complete details see the official doc issue at dotnet/docs#18875.
The text was updated successfully, but these errors were encountered: