The runic-app template (and dnx Runic.Create, which runs it) asks for the
host: --host cswebui, the default, --host desktop for Runic Desktop, or
--host desktop-gtk4 for Runic Desktop with GTK 4 and WebKitGTK 6 on Linux
(WithGtk4() from
Runic.Desktop.Gtk4;
on Windows and macOS it behaves like desktop). All use the same Window, Views,
and generated TypeScript clients; only Program.cs, the Window class, the host
packages, and the host script in index.html differ. Both Desktop hosts start
with DesktopEventLoop.Run(options, ...), which runs the application on the
event loop each platform needs.
For a starter walkthrough, see getting started
and the first Window example.
Runic.Application.CsWebUi
connects the generated Window and View contracts to a CS-WebUI presentation.
CS-WebUI remains a separately maintained upstream product, and applications can
also use its lower-level API directly.
Runic.Desktop is an independent presentation library for browser and embedded
WebView windows. Choose its embedded backend and fallback policy explicitly; its
package guide documents native
prerequisites. An existing CS-WebUI project does not switch to Desktop when a provider is
installed; compare a --host desktop project to see the changes.
Runic.Application.Desktop
connects generated Windows and Views to a Desktop surface. The
ReactiveUI first-window example
shows the browser client and scoped native Window lifetime.