GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — [Breaking change] Removal of built-in WinRT support in .NET 5.0 · Issue #37672 · dotnet/runtime

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

New issue
Copy link
New issue
Copy link
Closed
#36715
Closed
[Breaking change] Removal of built-in WinRT support in .NET 5.0#37672
#36715
Copy link
Labels
area-System.Runtime.InteropServicesbreaking-changeIssue or PR that represents a breaking API or functional change over a previous release.Issue or PR that represents a breaking API or functional change over a previous release.
Milestone
5.0.0

Description

@AaronRobinsonMSFT
AaronRobinsonMSFT
opened on Jun 9, 2020
Issue body actions

[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.

Reacted by lindexi, Gavin Williams, Nico Milcoff, Rafael Rivera and ysmgthntt

Activity

  1. AaronRobinsonMSFT
    added
    area-System.Runtime.InteropServices
    breaking-changeIssue or PR that represents a breaking API or functional change over a previous release.Issue or PR that represents a breaking API or functional change over a previous release.
    on Jun 9, 2020
  2. AaronRobinsonMSFT
    added this to the 5.0 milestone on Jun 9, 2020
  3. Dotnet-GitSync-Bot
    added
    untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
    on Jun 9, 2020
  4. AaronRobinsonMSFT
    removed
    untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
    on Jun 9, 2020
  5. Nukepayload2 commented on Jun 11, 2020

    @Nukepayload2
    Nukepayload2
    on Jun 11, 2020
    More actions

    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.

  6. svick commented on Jun 11, 2020

    @svick
    svick
    on Jun 11, 2020
    Member
    More actions

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

    Reacted by Nukepayload2
  7. AaronRobinsonMSFT commented on Jun 11, 2020

    @AaronRobinsonMSFT
    AaronRobinsonMSFT
    on Jun 11, 2020
    MemberAuthor
    More actions

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

    Reacted by Nukepayload2
  8. AaronRobinsonMSFT
    closed this as completedon Jun 18, 2020
  9. jaredpar
    added 2 commits that reference this issue on Jul 22, 2020

    Move to the .NET 5 SDK

    fd3535e

    Move to the .NET 5 SDK (#46038)

    d5fafa1
  10. ghost locked as resolved and limited conversation to collaborators on Dec 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-System.Runtime.InteropServicesbreaking-changeIssue or PR that represents a breaking API or functional change over a previous release.Issue or PR that represents a breaking API or functional change over a previous release.

    Type

    No type

    Projects

    No projects

      Milestone

      • 5.0.0

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.