Navigation Menu

Skip to content
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

Jump to bottom

[Breaking change] Removal of built-in WinRT support in .NET 5.0 #37672

Closed
AaronRobinsonMSFT opened this issue Jun 9, 2020 · 3 comments · Fixed by #36715
Closed

[Breaking change] Removal of built-in WinRT support in .NET 5.0 #37672

AaronRobinsonMSFT opened this issue Jun 9, 2020 · 3 comments · Fixed by #36715
Labels
area-System.Runtime.InteropServices breaking-change Issue or PR that represents a breaking API or functional change over a prerelease.
Projects
Interop-CoreCLR 5.0
Milestone
5.0.0

Comments

@AaronRobinsonMSFT
Copy link
Member

AaronRobinsonMSFT commented Jun 9, 2020 •
edited

[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.
@AaronRobinsonMSFT 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
@AaronRobinsonMSFT AaronRobinsonMSFT added this to the 5.0 milestone Jun 9, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Jun 9, 2020
@AaronRobinsonMSFT AaronRobinsonMSFT removed the untriaged New issue has not been triaged by the area owner label Jun 9, 2020
@jkoritzinsky jkoritzinsky mentioned this issue Jun 9, 2020
Merged
This was referenced Jun 9, 2020
Closed
Closed
@richlander richlander mentioned this issue Jun 10, 2020
Closed
@tommcdon tommcdon mentioned this issue Jun 11, 2020
Open
@Nukepayload2
Copy link

Nukepayload2 commented Jun 11, 2020 •
edited

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.

@svick
Copy link
Contributor

svick commented Jun 11, 2020

@Nukepayload2 You're supposed to use C#/WinRT for that. Have you tried it?

@AaronRobinsonMSFT
Copy link
Member Author

AaronRobinsonMSFT commented Jun 11, 2020 •
edited

@Nukepayload2 there are recommended next steps linked above in dotnet/docs#18875.

This was referenced Jun 12, 2020
Closed
Closed
@richlander richlander mentioned this issue Jun 15, 2020
Closed
@AaronRobinsonMSFT AaronRobinsonMSFT added this to To do in Interop-CoreCLR 5.0 via automation Jun 18, 2020
@AaronRobinsonMSFT AaronRobinsonMSFT moved this from To do to Done in Interop-CoreCLR 5.0 Jun 18, 2020
@SeeminglyScience SeeminglyScience mentioned this issue Jun 27, 2020
Closed
@ShankarBUS ShankarBUS mentioned this issue Jul 13, 2020
Closed
@AaronRobinsonMSFT AaronRobinsonMSFT mentioned this issue Jul 15, 2020
Merged
@jaredpar jaredpar mentioned this issue Jul 20, 2020
Merged
jaredpar added a commit to jaredpar/roslyn that referenced this issue Jul 22, 2020
@jaredpar
Move to the .NET 5 SDK
fd3535e 
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
@jaredpar
Move to the .NET 5 SDK (#46038)
d5fafa1 
* 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
Closed
Merged
@tebeco tebeco mentioned this issue Sep 15, 2020
Closed
@richlander richlander mentioned this issue Sep 22, 2020
Closed
@AaronRobinsonMSFT AaronRobinsonMSFT mentioned this issue Nov 30, 2020
Closed
This was referenced Dec 5, 2020
Merged
Closed
@dotnet dotnet 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.
Assignees
No one assigned
Labels
area-System.Runtime.InteropServices breaking-change Issue or PR that represents a breaking API or functional change over a prerelease.
Projects
No open projects
Interop-CoreCLR 5.0
  
Done
Milestone
5.0.0
Development

Successfully merging a pull request may close this issue.

Remove built-in WinRT support from the runtime jkoritzinsky/runtime
4 participants
@svick @Nukepayload2 @AaronRobinsonMSFT @Dotnet-GitSync-Bot