Unpackaged support for WinUI3 in WinAppSDK Preview 3!

@chendrixson what's the trick? Followed the doc and now luck. Fails to load the ui xaml assembly

@dotMorten Could you be hitting this?

@chendrixson nope ran the installer

@chendrixson anyway just going through the motions and can't help thinking this entire "package first" approach is upside down. Imho packaging should be an optional add-on project you choose to add, just like it has been for Win32 apps for a long time already.

@chendrixson ie there shouldn't be any packaged winui templates. There should just be unpackaged and if you want to package it, you go and add a standard packaging project like you always have. It all feels rather hacky and hobbled together as it is now

@dotMorten @chendrixson I prefer packaged winui template though. Single-project packaged app template also fixes all those "Why is my app not running" questions in github when devs forget they should launch the packaging project. Also, as a user (of the OS), package-first is good for me

@srvzox @dotMorten @chendrixson Except people go to your releases and download the msixbundle and then report issues when it doens't install because it's missing dependencies. Need to redirect them back to where they downloaded that and install the dependencies which are also uploaded.

@beeradmoore @dotMorten @chendrixson That's weird, in my own testing (on 3 other non-dev machines at home) WASDK would be installed before our app in the app installer. Are all of your users facing the same issues? D:

@srvzox @dotMorten @chendrixson Only the people who go to GitHub releases page and download a single file instead of the dedicated downloads page (which has a .appinstaller) Ohh.. maybe I should be putting that .appinstaller in the releases and hoping people get that instead of msixbundle ?

@sy1ve0n @srvzox @dotMorten @chendrixson 🙏🏻 yes! This makes so much sense. I will do that for the next release. Thanks!