Use ControlGallery to explore controls and ModernFormsNext.DemoApp to learn the recommended starter structure. Explorer and Outlaw demonstrate larger desktop layouts. Windows is the primary runtime target; the shared Windows/Android sample has a separate, experimental Android host.
Run the commands below from the repository root with the SDK selected by global.json.
| Application | Purpose |
|---|---|
| ControlGallery | Controls, layout, rendering, themes, input, and visual regression checks. |
| Explorer | File browsing, ribbon groups, tree navigation, and icon lists. |
| Outlaw | Mail-style navigation, toolbars, and an owner-drawn message list with sample data. |
| ModernFormsNext.DemoApp | Minimal template/reference application. |
| ModernFormsNext.DesignerPlayground | Standalone Designer development and manual checks. |
| ModernFormsNext.CrossPlatform.Sample | One shared control tree hosted on Windows and Android. |
| ModernFormsNext.Android.SmokeTest | Technical Android lifecycle, manifest, and permission checks. |
The main visual gallery covers buttons, inputs, checked and selectable lists, rich text, Markdown, menus, tooltips, containers, and layout elements. The screenshot shows the DataGridView page with cell selection, row headers, and a second data-bound grid.
dotnet run --project .\samples\ControlGallery\ControlGallery.csprojThe Animations and Interaction Effects page demonstrates pointer- and center-origin ripple, rapid bounded waves, press scale, hover/focus/disabled transitions, sequence, parallel, timeline, keyframes, repeat, auto-reverse, custom definitions and interpolators, cancellation, replacement policies, reduced motion, animations disabled, and scheduler/ripple diagnostics. It is opt-in and restores the animation policy when unloaded.
The Carousel / Refresh page demonstrates collection utilities: 100,003 recyclable interactive pages, jump/navigation, source moves, axis changes, and a borrowed AsyncCommand with explicit completion and cooperative cancellation.
The Pages and navigation page demonstrates hosted pages, retained stack entries, canonical validation veto, shared-scheduler appearance and scoped Back. Its application policy disposes pages after removal; framework Pop itself transfers without disposal.
The Tabbed / Flyout pages page demonstrates page composition: retained editable tabs, add/remove/move, Auto/Overlay/Split modes, canonical dismissal and independent local directions. Its Open navigation action is inside the detail page; the sample owns disposal after removal.
The MarkdownEditor page demonstrates Editor, Preview, and Split modes, the public command
toolbar, Ctrl+K, hosted link and image request dialogs built only from ModernFormsNext controls,
preview link forwarding, and optional proportional scroll synchronization. Its source includes
editable links and images, Unicode, local and HTTP image sources, and enough content for manual
scroll testing. The hosted image dialog can insert a reference unchanged or choose a local raster
image with the ModernFormsNext file picker and copy it into MarkdownEditorAssets beside the
sample output. Collision handling is selectable; no source-repository directory is modified.
The editor also demonstrates list-aware Enter/Tab/Backspace, AltGr-safe shortcuts, and undo/redo.
Explorer demonstrates ribbon groups, theme choices, a directory tree, and a file list. The screenshot shows the Windows system directory. Directory navigation is implemented; several ribbon actions deliberately show a "Functionality not available in demo" message.
dotnet run --project .\samples\Explorer\Explore.csprojThe directory is named Explorer, while the project file is Explore.csproj.
Outlaw demonstrates a mail-style layout with navigation, tabbed toolbars, an owner-drawn message list, and a placeholder reading pane. The messages are generated sample data; this is a UI example, not a connected mail client.
dotnet run --project .\samples\Outlaw\Outlaw.csprojThe template/reference application validates that the default generated application stays clean,
minimal, beginner-friendly, and aligned with ModernFormsNext.Templates. Control experiments and
visual regressions belong in ControlGallery.
dotnet run --project .\samples\ModernFormsNext.DemoApp\ModernFormsNext.DemoApp.csprojSee getting started and installation.
The standalone host is for Designer development and manual validation. Running it does not replace verification of the Visual Studio extension and its out-of-process host.
dotnet run --project .\samples\ModernFormsNext.DesignerPlayground\ModernFormsNext.DesignerPlayground.csprojSee Designer architecture and Visual Studio host.
A multi-target project organized around shared App, MainForm, and MainPage files plus thin
Platforms/Windows and Platforms/Android hosts. Both targets use the same real ModernFormsNext
control tree. Android calls Application.Run(Form) through its registered IWindowingPlatform
and backend-owned Activity/Skia presentation, with one main Form, owned modals, and reusable popups.
.\scripts\windows\Run-CrossPlatformSample.ps1
.\scripts\android\Run-CrossPlatformSample.ps1 -DeviceId <serial>See the cross-platform sample guide and Android support matrix for prerequisites and current limitations.
This technical host exercises Android lifecycle, manifests, permissions, and backend integration. Use the Android development guide for setup and the release validation matrix for the scope of device evidence.
The Windows images above were refreshed on 2026-09-27 from the source checkout, at 100% display scaling. See screenshot provenance and refresh guidance for the source revision, capture details, and historical images. Historical Linux/macOS images are not evidence of current platform support.