Getting started
Install Elarion, get one handler onto the wire, and learn the project layout the generators expect.
This section takes you from an empty solution to a working, source-generated endpoint. Follow the three pages in order — each builds on the last.
Installation
Add the runtime packages and source generators to an application project and an ASP.NET Core host.
Quickstart
Build your first module and handler and call it over a JSON-RPC endpoint — a few minutes, no database.
Project structure
The solution layout and naming conventions the generators rely on, and the dependency direction that keeps your application independent of the host.
Where to go next
Build a real app
A full end-to-end tutorial: a modular billing backend with a typed React frontend.
Understand the model
Handlers, results, modules, and the source generation that wires them — the mental model behind everything else.
Don't learn from pre-generator examples. Older Elarion codebases predate the current generator
model: they vendor an older copy of Elarion and hand-write the per-module
services.AddXHandlers() / AddXServices() registrations that [GenerateModuleBootstrapper] and the
generated ConfigureDefaultServices now emit for you — copying that pattern onto current packages
duplicates registrations the generator already emits (see Modules). Use the
tutorial and its compiled billing sample under
samples/Billing as the current
reference instead. One gap to know about: the billing sample authenticates with JWT bearer tokens, so
the ASP.NET Identity path has no sample of its own yet.