Open DmitryBorodiy opened 1 week ago
Maybe anyone knows how to fix this?
We use a separate git branch for MSIX packaging in which TargetFrameworks is replaced by single TargetFramework in order for the build to succeed in the CI pipeline. Would be also great to fix this in VS by eventually respecting the target framework selected in the Debug dropdown.
Project MSIX SDK
Describe the bug Hello, community! I have sample Avalonia application project with multiple target frameworks monikers.
Expected behavior The MSIX packaging project must support multiple target frameworks or prefer net8.0-windows target framework monikers.
Screenshots![image](https://github.com/microsoft/msix-packaging/assets/57910623/82013fdf-d36a-427d-b6d9-9e0d72f8e36f)
Platform .NET/Avalonia, Windows 11 build 22635