Changing a xaml file in the shared library does not trigger a wasm project rebuild

[unoplatform]

Changing a xaml file in the shared library does not trigger a wasm project rebuild

[jeromelaban]

This is a known issue for the change tracking, but in the case of the playground, it's simply misconfigured.

See here: https://github.com/nventive/Uno.Playground/blob/80322aec3d759d009f6a900bca4a07bc63ae6a62/Uno.UI.Demo.WASM/Uno.UI.Demo.WASM.csproj#L24

You can point to the Xaml files coming from the shared project, and VS is going to honor that.

[ghuntley]

Closing this out as XAML Hot Reload is now in preview, check out https://platform.uno/announcing-uno-platform-2-0/ for more information.

Uno Platform

Announcing Uno Platform 2.0 - Uno Platform

When we initially open sourced Uno Framework at //build 2018, we took a big step in showing the world what we had been internally working on for nearly five years. The year was 2018 and we were still doing mostly mobile work via UWP.  During those days, you saw us fly the #UWPEverywhere banner proudly. A lot has changed since then in the .NET ecosystem, in WebAssembly world, as well as in scenarios our community had been asking us to cover. While UWP was, and still is, our first love, with today’s announcements we are keeping pace with our audience asks and we are shifting gears towards ensuring the future WinUI stack can be run everywhere – WebAssembly, iOS, Android, and of course Windows, making room for our new northern light – #WinUIEverywhere!!!  In practice, what does that mean? Announcing XAML Hot Reload for Uno Platform Preview The inner loop for developing with Uno gives you the ability to use XAML Hot Reload in Visual Studio for Windows, allowing you to go to 95% of your app’s development. You generally need to finalize your application’s testing using the actual app environment, on device or in a browser.  The ability to Hot Reload XAML from Visual Studio while the app is running, will give for the ability to update the …