Windows Unpackaged support in .NET MAUI

[mattleibow]

Description

This is an epic issue tracking all the things needed for a 100% support rating.

MAUI SDK

• Controls / XAML
• Core
• Essentials
  • Add support for SecureStorage in Unpackaged apps #10476
  • Fix FilePicker on Windows Unpackaged #10356
  • Determine which Essentials work in Windows Unpackaged apps #8552
• Graphics
• Other (targets, resizetizer, etc)
  • Add Support for WinUI Unpackaged Apps #3166
  • Publish Unpackaged Apps Error(Project Reference MAUI Library ) #9064
  • Use the WASDK self-contained by default #8432
  • Shell on Windows: Icons not shown #6330
  • Unable to run Windows application from command line #5975
  • Publishing an unpackaged Windows app fails by default #5881
  • Initial work to get unpackaged WinUI apps #4460

Platform SDKs (Windows App SDK, Windows OS)

• Unable to run Windows application from .NET SDK command line microsoft/WindowsAppSDK#2922
• Setting WindowsPackageType to None makes Visual Studio think it is missing SDK references microsoft/WindowsAppSDK#2870
• Self contained apps fail to build with AnyCPU & RIDs microsoft/WindowsAppSDK#2684
• Provide a way to run winui apps from dotnet cli microsoft/microsoft-ui-xaml#7331
• WinUI custom titlebars not draggable in unpackaged apps
  https://dev.azure.com/microsoft/OS/_workitems/edit/38358053
  https://microsoft.visualstudio.com/OS/_workitems/edit/37749544
• Unpackaged apps can get Package Identity without any developer engagement.
  https://dev.azure.com/microsoft/OS/_workitems/edit/40211194
• Label:[WinUI] FontFamily is not recognized in Unpackaged application. #9104
• dotnet publish results in an error about duplicate files microsoft/WindowsAppSDK#3337
• Passing MSBuild properties on the CLI throws errors microsoft/WindowsAppSDK#4008
• Self contained apps fail to build with AnyCPU & RIDs microsoft/WindowsAppSDK#2684

Tooling

• Core IDE
  • [MAUI] Enable WinAppSDK automatic packaged->unpackaged setting in Visual Studio
    https://dev.azure.com/microsoft/OS/_workitems/edit/37055170
• UI Tools
• Platform Tools
  • ClickOnce support?
• Other
  • Make unpackaged the DEFAULT development experience
  • .NET MAUI WinUI publishing "unpackaged" apps
    https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1556834
  • Unpackaged app created from default template just crashes
    https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1565698
  • Customer needs a modern installation experience for desktop applications using an Open Source deployment solution
    https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1256825
  • Developers can publish/deploy unpackaged
    https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1054423
  • Add build support for unpackaged perf scenarios
    https://dev.azure.com/microsoft/OS/_workitems/edit/39145956
  • Customize and optimize .NET MAUI apps for packaging and distribution
    https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1556844
  • [VS] WinUI Unpackaged support investigation and planning
    https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1555666

Runtime / .NET SDK

• [ ]

VS bug #1791241

[kevmoens]

I would like to up vote ClickOnce
We ship software to on premise customers which then install and host our apps. Thus we don't know the customer's URL where are app is hosted.

Currently we can update our app.config so our app knows where the hosted services are. Then ClickOnce solves this as we package the ClickOnce app on their server using mage.exe with their own server's URL.

[ghost]

We've added this issue to our backlog, and we will work to address it as time and resources allow. If you have any additional information or questions about this issue, please leave a comment. For additional info about issue management, please read our Triage Process.

[Xo3-ToBapbl]

Could some please clarify: am I right that currently it is not possible to debug MAUI Win UI unpackaged application?

[mattleibow]

.NET MAUI supports building, debugging and publishing unpackaged apps. I am closing this issue as it was more of a container/uber issue to link everything. However, all the main features are done and the remaining are logged with the related teams. For example, issues with publishing certain things or running from the CLI are logged with WASDK.