Launcher Views

All XAML lives under sources/launcher/Stride.Launcher/Views/ plus the specialized Crash/ folder. Compiled bindings are on by default (<AvaloniaUseCompiledBindingsByDefault>true</AvaloniaUseCompiledBindingsByDefault>) so every DataContext is typed.

Main window

• MainWindow.axaml is the Window shell. Its code-behind wires the window handle back to MainViewModel.WindowHandle so it can be passed to Game Studio via /LauncherWindowHandle.
• MainView.axaml is the content UserControl. It hosts the version list on the left, the tabs (Versions / Recent projects / News / Documentation) on the right, the announcement overlay, and the bottom bar with the Start Studio / Install buttons. MainView.axaml.cs has an EditorChanged handler that saves the user's editor choice to LauncherSettings.PreferredEditor immediately; the runtime combo binds to MainViewModel.SelectedRuntime, which saves on its own.

Splitting the Window from a UserControl lets Avalonia's designer render MainView in a SingleViewApplicationLifetime (see App.OnFrameworkInitializationCompleted's second branch).

Announcement overlay

Announcement.axaml is bound to MainViewModel.Announcement. When the view model is non-null, the overlay renders its markdown through the shared MarkdownViewer. The user can dismiss it or tick "don't show again", which calls back through MainViewModel.SaveTaskAsDone.

Self-update window

SelfUpdateWindow.axaml is a small modal progress dialog. SelfUpdater creates it via dispatcher.InvokeAsync, calls LockWindow() to prevent the user from closing it during critical file operations, and calls ForceClose() if the update fails. See self-update.md.

Crash report

Under Crash/:

• CrashReportWindow.axaml — the dialog. Shows the exception summary, a toggleable details pane, and buttons to copy the report or open a new GitHub issue.
• CrashReportViewModel.cs — the view model. Formats the CrashReportData for display, uses the clipboard delegate passed in by Launcher.CrashReport (set to window.Clipboard.SetTextAsync), and exposes CopyReportCommand, OpenIssueCommand, ViewReportCommand, CloseCommand.
• CrashReportData.cs and CrashReportArgs.cs — the serializable shapes passed between the exception handler and the view.

The crash report runs under a brand-new MinimalApp, because the main App is typically in the middle of shutting down.

Converters

Two converters live next to the views instead of in the ViewModels folder because they are UI-only:

• ProgressToIndeterminatedConverter.cs — returns true when progress is unknown so the ProgressBar flips to indeterminate mode.
• EditorNameConverter (in ViewModels/ but used in XAML) — see viewmodels.md.

Markdown rendering

Every MarkdownViewer in the launcher shares a single pipeline configured once in App.InitializeMarkdownViewer:

• Markdig extensions: abbreviations, alert blocks, figures, footnotes, media links, plus the generic UseSupportedExtensions.
• MarkView extensions: TextMate syntax highlighting, SVG, Mermaid.
• A global LinkClickedEvent class handler routes every <a> click through Process.Start(..., UseShellExecute = true) so URLs open in the user's browser rather than inside the app.

This is how release notes, announcements, and error dialogs get consistent rendering.

Where to put new XAML

• New tab in the main window → extend MainView.axaml with a new TabItem and bind its content to a new property on MainViewModel.
• New modal dialog → create an Avalonia Window with its own view model and show it through IDialogService (so tests can stub it).
• New crash surface → do not add more MinimalApp spawn sites; reuse CrashReportWindow and extend CrashReportData/CrashReportViewModel.