Open BrandonStudio opened 1 year ago
It appears the Windows App SDK does not support building a msixbundle from dotnet.
@evelynwu-msft do we have anymore info?
internal issue: https://dev.azure.com/microsoft/OS/_workitems/edit/31482969
Been hacking away at this and I think I got something that will make this all work wonderfully:
https://gist.github.com/mattleibow/8332ed79b569c9d7bbdae64a6e8142a6
If we get some testing on this we may be able to include somewhere until the WASDK issue is resolved.
@mattleibow is it for build only? Is it for CLI only? Can I publish my project as bundle in Visual Studio?
I do not believe there is a way to publish using this from the IDE, but the CLI will work.
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
I do not believe there is a way to publish using this from the IDE, but the CLI will work.
@mattleibow how can I use your workaround to generate a '.msixupload' file to be able upload to the Microsoft Store? We're getting ready to release and I feel like I'm about to tell management that after all our work to start on this endeavor we won't be able to release. Here is what I'm currently using based off of the original Xamarin.Forms app that we moved to MAUI:
>dotnet.exe publish MyApp.csproj --framework net8.0-windows10.0.22621.0 --configuration Release --self-contained -nologo -nr:false -nologo -nr:false -p:AppxBundle=Always;UapAppxPackageBuildMode=StoreUpload;AppxBundlePlatforms="x86|x64"; /t:GenerateMsixBundle
Description
Visual Studio can now only publish single target msix, but I'd like to create multi-targeting app (both x64 and ARM64 or more) all in once. It seems there is no way to do this
Public API Changes
It's a problem of build tools, there's nothings to do with API
Intended Use-Case
Same as above
Depends on