Rast.AdminWeb 2.2.1

Rast.AdminWeb

The command deck for operators and builders.

Rast.AdminWeb is the Blazor admin application layer of RAST: the host UI (layouts, navigation, identity wiring) plus ready-made system pages that talk to the database through EF Core—users, roles, tenants, localization, menu/page registry, module and entity configuration, and more. It is the piece you run as the operator console; business modules (CRM, orders, etc.) attach alongside or consume the same patterns.

Ready-made areas (examples)

Menus, permissions, and many routes are driven from RastSysContext (and related metadata), not hard-coded only—so operators evolve the app from the DB (plus migrations), within the RAST security model.

Database providers (system / admin DB)

DatabaseSettings:DBProvider selects the EF Core provider for RastSysContext:

The shared constants also define sqlite (DbProviderKeys.SqLite), and helpers exist for SQLite-flavoured JSON columns; SQLite for RastSysContext is not enabled in the default SysDbRegister switch (branch is commented)—turn it on only after wiring UseSqlite and a SQLite migrator project to match your solution.

Application databases (per-app DbContexts) follow the same provider key idea in consuming hosts; see your web app’s DI and migrator layout.

Rast.AdminWeb ships the admin web shell of RAST—layouts, navigation, shared pages, and the scaffolding that turns a pile of modules into something navigable. This is where the product stops feeling like a demo and starts feeling like infrastructure.

Why RAST Blazor shines here

RAST Blazor is built for real business, not toy dashboards: multi-module admin, role-aware navigation, inquiry and maintenance at scale, and room for complex workflows (approvals, hand-offs, long-running operations) without the UI collapsing under its own weight. You manage messy scenarios—many entities, many screens, many rules—with a single coherent shell instead of a dozen one-off SPAs.

What ships here

• Layouts, menus, and cross-cutting admin UI tuned for line-of-business density
• Sample and system-oriented forms that show how RAST models complexity
• The connective tissue between Rast.UiLibrary, Rast.Templates, and your own modules
• A foundation for workflow-aware experiences (editors, steps, operator tools) alongside classic CRUD

Vibe

Serious tools deserve quiet confidence: fast loads, obvious hierarchy, and enough polish that power users stop fighting the chrome—while the business story (who does what, in which order) stays legible.

Requirements

• .NET 9
• ASP.NET Core / Blazor host (see your solution’s web head)

A flagship slice of the RAST Framework.