Using the WindowsAppSdk for packaging in a single project wpf app with Blazor Hybrid doesn't compile

Open

#5,956 opened on Oct 30, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-WebView needs-triage

Dominant language: C++
Stars: 4.7k
Forks: 471
Avg merge: 3d 13h
Merged PRs (30d): 28

Description

### Describe the bug

If you add the WindowsAppSdk.Runtime for the packaging of a single project WPF app this works and produces an msix. However, adding Blazor Hybrid to solution seems to confuse Webview 2 and the components for Blazor Hybrid suddenly become unavailable.

### Steps to reproduce the bug

1. Setup a WPF single project msix app
2. Add Blazor Hybrid (v9+)

### Expected behavior

The app should build an MSIX.

### Screenshots

_No response_

### NuGet package version

Windows App SDK 1.8.2: 1.8.251003001

### Packaging type

Packaged (MSIX)

### Windows version

Windows 11 version 24H2 (26100, June 2025 Update)

### IDE

Other, Visual Studio 2022

### Additional context

_No response_

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

Reproduce the setup with a single-project WPF MSIX app, Windows App SDK 1.8.2, and Blazor Hybrid v9+. Start by adding Blazor Hybrid to the packaging configuration and inspect the resulting WebView2 and component build errors. Done means the application builds successfully and produces an MSIX.

Written by the indexing model from the issue text.

Assessment

Domain: build-system, desktop
Issue type: Bug
Difficulty: 4/5
Estimated time: 3-5 days
Activity status: Stale
Clarity: Mostly clear
Newbie friendliness: 35/100