MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Feature]: Opting out of WindowsAppSDK detection
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Describe the feature/enhancement you need
I am using WebView2 on WPF and also want to install WindowsAppSDK. WebView2 automatically update the APIs to WinRT version. We would like it not to do that when I am not developing on WinUI 3.
The scenario/use case where you would use this feature
I am using WebView2 on WPF. However, I also want to use WindowsAppSDK for some of the Windowing APIs like AppWindow, as some APIs are easier to work with. We're currently stuck in older version of WindowsAppSDK and WebView2 due to the auto detection. I don't need WinRT version of the WebView2 API.
Current impact to me is that I am stuck with earlier version of both packages when the detection is not there, and use allias.
How important is this request to you?
Impactful. My app's user experience would be significantly compromised without it.
Suggested implementation
Some flags in csproj like possibly <UseWebView2WinRT>false</UseWebView2WinRT>
What does your app do? Is there a pending deadline for this request?
My app is a lightweight progressive web app. We would like the windowing part to be lightweight while presenting user with web app.
Contributor guide
No contributing guide indexed for this repository
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 tracing the WindowsAppSDK detection behavior and the project settings represented in the csproj. Confirm how WebView2 selects its WinRT APIs for WPF applications, then define and validate an opt-out that preserves the existing behavior when unset and allows the non-WinRT path when disabled.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100