microsoft / microsoft/msix-packaging
[BUG] Error when trying to package project with multiple TargetFrameworks
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 193
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
Project
MSIX SDK
Describe the bug
Hello, community!
I have sample Avalonia application project with multiple target frameworks monikers.
<PropertyGroup>
<OutputType>WinExe</OutputType>
<TargetFrameworks>net8.0-windows10.0.19041.0;net8.0</TargetFrameworks>
<ApplicationManifest>app.manifest</ApplicationManifest>
<Nullable>disable</Nullable>
<PlatformTargets>x86</PlatformTargets>
<Platforms>x64;x86;</Platforms>
</PropertyGroup>
Expected behavior
The MSIX packaging project must support multiple target frameworks or prefer net8.0-windows target framework monikers.
Screenshots
Platform
.NET/Avalonia, Windows 11 build 22635
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 failure using the Avalonia project configuration shown in the issue, with both net8.0-windows10.0.19041.0 and net8.0 target frameworks on Windows 11. Start by locating the MSIX packaging project behavior for multi-targeted projects; done means packaging succeeds with multiple target frameworks or consistently selects the Windows target framework.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100