Uno QuickStart Environment

[michael-hawker]

Can we have a browser-based view something like https://github.com/unoplatform/Uno.QuickStart to make it easier to browse experiments?

Can we do something where we only show the UWP head in VS and then the WASM head if in the browser? How do we not overload a developer with multiple heads when trying to develop a feature? Is there an easier way to select which head to run?

[XAML-Knight]

Can we have a browser-based view something like https://github.com/unoplatform/Uno.QuickStart to make it easier to browse experiments?

Like this idea, as WebAssembly is one of Uno Platform's key selling points. Using one of the new GitHub Codespaces, with VS Code, is something the Uno people are advertising.

Can we do something where we only show the UWP head in VS and then the WASM head if in the browser?

Sounds good - not sure what technology we could rely upon to do this for us dynamically, other than giving devs a heads-up in a readme file on which environment any individual project should be opened in.

[Arlodotexe]

Can we do something where we only show the UWP head in VS and then the WASM head if in the browser?

Should be noted that WASM can be launched and debugged when in Visual Studio

[shweaver-MSFT]

I think Uno makes a lot of sense so long as we can abstract the extra bits and not include them in each labs project. Maybe you could build a POC Uno app that loads a page from another child UWP project. You might need a script or source generator as a pre-process step.

I imagine the Uno app as the uber solution that load all the labs projects, and the child project represents an individual labs project. What do you think?

[Arlodotexe]

If we want each sample to be runnable under Uno on its' own, the entrypoint (App.xaml.cs) for each sample app either needs to:

• Be in a shared project, shared between the UWP and WASM heads
• Be copied into a separated WASM-only project using a build script.

edit: this is handled now

[XAML-Knight]

Take a look at @Arlodotexe's PR: #11

[Arlodotexe]

#16 will be a big part of providing this experience.

[michael-hawker]

Think we've accomplished this with the codespaces work, so going to close.