Cornerstone 3.0.277.37790

<img align="left" src="https://github.com/BobbyCannon/Cornerstone/blob/master/Cornerstone.png?raw=true" height="64" width="64" style="margin-bottom: 8px; margin-right: 8px;" />

Cornerstone is a shared .NET 10 framework for desktop and cross-platform apps: process bootstrap, Keystone (Bus, State, Engine), lifecycle, sync and storage, and an optional UI runtime. Markup is .cxaml, compiled at build time.

Shape of an app

Process entry builds one stack. Domain work stays in Keystone. Presentation is optional.

Process entry (console / desktop / mobile / browser / service)
  └─ AppBootstrap.Initialize(…)     process DI, runtime info, platform
       └─ App services
            ├─ Keystone — Bus : State : Engine
            ├─ Lifecycle — Initialize → Load → Start → Process → Stop → …
            ├─ Sync and storage
            └─ Presentation (optional)
                 ├─ ViewModels + ViewIntegration
                 └─ AppDispatcher (attached ViewModels)

State is the model. The engine's processors mutate that state. The bus carries the messages. Processors run off the UI thread. When a view is attached, ViewModels and AppDispatcher project that state onto the screen.

Native controls without compromise

Most UI stacks treat native controls as a foreign window glued on top of everything else. Buttons, menus, and popups cannot sit over a live WebView, map, or video. Workarounds are snapshots, pause-and-cover, or "don't overlap." You are expected to pick: native content, or a real UI.

Cornerstone does not make that trade. Native and Cornerstone controls live as peers — equal in every way. A WebView, a map, a video player, and a toolbar are just controls in the same tree. You can stack them, overlap them, and mix first-party and third-party native SDKs without giving one side of the UI away.

Details: Native layering.

See it

Sample apps in Applications/ run on Desktop, Android, iOS, and in the browser. Projects in Integrations/ host a third-party SDK. An app takes an integration with a project reference and builds it from this tree. Each SDK keeps its own license.

Start

dotnet new install Cornerstone.Templates
dotnet new cornerstone.app -n MyApp

A UI app references Cornerstone and Cornerstone.Presentation. The analyzer ships inside Cornerstone, so both references are required to compile .cxaml. Default theme and product controls are already in Presentation. Entity Framework, PowerShell, and automation ship as their own packages.

Templates: Cornerstone.Templates/README.md. Documentation: Cornerstone.Documentation/Readme.md.

The aim is a framework for developers by developers: fast, open, free, and reliable, and software that makes building applications enjoyable. A release may miss a goal. If you run into an issue, we would love to hear about it.

License

Cornerstone is MIT. See license.txt.

Cornerstone.Presentation includes source from the other projects. The upstream license and the other third-party notices are in Cornerstone.Presentation/NOTICE.md.