What Cotomy Tries to Solve
Structural problems in long-lived business UI systems and why Cotomy exists.
Notes on building a DOM-first UI runtime for long-lived business applications.
New to Cotomy? Start with the core problem, the design philosophy, and the runtime behavior.
Structural problems in long-lived business UI systems and why Cotomy exists.
The architectural decisions behind a DOM-first UI runtime.
Usage-focused articles showing how the runtime behaves in real screens.
The latest entries across the Cotomy blog.
A practical guide showing how I usually structure search screens, edit screens, and read-only screens in Razor Pages with Cotomy.
Cotomy project templates for Razor Pages are now available in Standard and Professional editions. They are designed for CRUD-heavy business applications where teams want to avoid rebuilding page structure, form flow, authentication, and persistence from scratch.
In CRUD screens, the core problem is often not where state is stored, but whether the mutation path is defined. Once load, input, save, and reload are allowed to diverge, the screen becomes difficult to reason about.
Server-side postback screens were limited, but they kept one execution path. Once Ajax became the main update mechanism, keeping display, input state, and server truth aligned became a structural problem.
State failures in business UIs are usually not isolated bugs. They appear when DOM state, in-memory state, and server state have no explicit ownership and synchronization rules.
Why I moved from natural keys to surrogate keys, and why that change made both database design and application code easier to manage.
Explore the Cotomy Series. View all series →
Structural problems in web application development and the architectural ideas that led to Cotomy.
Articles discussing architectural decisions and design philosophy behind Cotomy.
Practical guides for building screens and workflows with Cotomy.
Development stories and architectural turning points behind Cotomy.
Usage-focused articles showing how Cotomy APIs behave in real screens.
Articles about C# architecture decisions connected to long-lived business systems.
Release and usage articles for the Cotomy Razor Pages project templates.
Essays, industry observations, and development experiences across software work.
Version history and release updates for Cotomy.
Patch release that simplifies default bind generator state handling and refreshes release-note references.
Patch release adding page-level default bind name generator support.
Patch release restoring attached semantics and adding isConnected support in runtime behavior.
Release focused on attached-state consistency updates and reference/documentation alignment.
Patch release that fixes request keepalive handling on page unload.
First stable major release. Establishes Cotomy as a production-ready foundation for business web applications.