microsoft / microsoft/microsoft-ui-xaml

Microsoft.WindowsAppSDK.WinUI v2.3.2 is not capable with Microsoft.WindowsAppSDK.Runtime v2.3.1

Open
#11,252 3 comments 7 reactions 0 assignees View on GitHub
area-NugetPackage bug
Dominant language
C++
Stars
8.4k
Forks
942
Avg merge
2d 7h
Merged PRs (30d)
105

Description

### Describe the bug

Use Microsoft.WindowsAppSDK.WinUI v2.3.2 with Microsoft.WindowsAppSDK.Runtime v2.3.1 cause build errors

```xml
<_VersionMismatch Include="Microsoft.WindowsAppSDK.WinUI"
Condition="'@(_PackageInfo->WithMetadataValue('PackageName', 'microsoft.windowsappsdk.winui'))' != '' and
'@(_PackageInfo->WithMetadataValue('PackageName', 'microsoft.windowsappsdk.winui')->Metadata('PackageVersion'))' != '2.3.0'">
2.3.0
@(_PackageInfo->WithMetadataValue('PackageName', 'microsoft.windowsappsdk.winui')->Metadata('PackageVersion'))

```

```
One or more referenced Windows App SDK components are newer than the versions expected by the Microsoft.WindowsAppSDK.Runtime package: Microsoft.WindowsAppSDK.WinUI: Microsoft.WindowsAppSDK.Runtime expected version 2.3.0, but version 2.3.2 was referenced. Please update the component references to match the versions expected by the Microsoft.WindowsAppSDK.Runtime package, or set 'true' to make the project self-contained.
```

### Why is this important?

Microsoft.WindowsAppSDK.Runtime should capable with Microsoft.WindowsAppSDK.WinUI

### Steps to reproduce the bug

1. Disable self contains
2. Install Microsoft.WindowsAppSDK.Runtime v2.3.1
3. Install Microsoft.WindowsAppSDK.WinUI v2.3.2
4. Build the project

### Actual behavior

_No response_

### Expected behavior

_No response_

### Screenshots

_No response_

### NuGet package version

None

### Windows version

Windows 11 (25H2): Build 26200

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Begin with the listed reproduction steps using Microsoft.WindowsAppSDK.Runtime 2.3.1 and Microsoft.WindowsAppSDK.WinUI 2.3.2 with self-contained deployment disabled. Inspect the package version metadata and the build-time version check that emits the shown error; done means the supported package combination builds without an incorrect mismatch failure.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.