microsoft / microsoft/AdaptiveCards
[Feature Request] WinUI 3 renderer should support .Net8
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Problem Statement
Without .Net8 support, anyone using the .Net8 renderer is stuck using the old win10-xxx style RIDs, which can cause other problems.
Proposed solution
Now that WinAppSDK has updated, we should be able to update too.
Alternatives or Workarounds
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the WinUI 3 renderer project and its WinAppSDK or runtime configuration. Check how the renderer currently targets .NET and uses Windows runtime identifiers, then verify the updated configuration with the renderer's existing build or test workflow. Done means .NET 8 projects can build and run with the current WinAppSDK without relying on old win10-style RIDs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100