What's the best way to incorporate a Cross-Runtime Library (WinUI) into the new project structure

[ToddGlodek]

So let's say I have a WinUI & WASM project - and I want to use a cross runtime project to define controls which I will re-use again in other projects. Let's assume that for a variety of reasons, I need to make a customization to the WASM controls that are in the library. I setup both the main TestMe & TestMe_Library projects in my solution - and establish a project reference.

Then I modify the MyCustomControl in the library and add it to the MainPage in the solution. Now I want to see the customized control in the browser. However, the WASM-specific customization is nor displayed.

• Are we supposed to create a second TestMe.csproj file that specifically references the TestMe_Library.WASM.csproj?
• Would that second/alternate project referenced in the main TestMe.Wasm head instead ??

I tried a variety of different approaches - but always ran into a build error related to problems in the auto-generated code.

What would be super awesome would be to modify the Template Wizard to present the option of including a Cross-runtime library in the newly created solution file. This would be all pre wired for the various options: Skia/WASM/etc. This would provide first-time users with an example of the best way to do it.

Perhaps in a future Live-Coding session you could go through the process. Having a short HOW-TO reference video on the web would also be really useful for first-time Uno Platform users.

[ToddGlodek]

I guess it's related to this "HAS_UNO_WASM does not work in latest project template" #11763

[limeniye]

About last one.
You can subscribe to the similar issue: unoplatform/uno.templates#503