Getting Started
Use this section to understand the structure of a complete RecroGrid Framework solution, choose the application model, and then follow the corresponding setup workflow.
A modern RecroGrid Framework solution combines a browser-facing application, a dedicated backend API, Entity Framework data access, and the database. The backend API is a required application in both modern Blazor-based application models: it hosts the main RecroGrid Framework server runtime, most business logic, Entity Framework integration, and database operations.
For new development, the recommended model is the Server-side Application. Before creating the projects, review the available application models so the solution structure, authentication flow, and API access pattern are clear from the beginning.
Tip
To explore a complete working solution, start from the RecroGrid Framework Demo on GitHub. The demo covers the backend API, Blazor-based application variants, the legacy MVC integration path, and the Northwind sample database.
Complete solution foundation
The recommended Server-side Application consists of a browser-facing Blazor host application, a dedicated backend API application, and the database:
flowchart TD
browser[Browser]
host[Blazor host application]
api[Backend API application]
db[(Database)]
browser --> host
host --> api
api --> db
The Blazor host manages OpenID Connect sign-in, the authenticated session, and proxy access to the backend API. During development, the Blazor application has both a host/server part and an interactive client part. The separate backend API application owns the main RecroGrid Framework server runtime, most business logic, Entity Framework integration, and database operations.
The Server-side Application workflow follows this dependency direction: the backend API and its data-access foundation are established first, followed by the browser-facing Blazor application and the integrated client-server configuration.
Choose the application model
An application model defines how the browser-facing UI, authentication, API access, and RecroGrid Framework server runtime are divided between deployed applications. The Application Models page presents the supported models from deployment, development, authentication, and request-flow viewpoints and highlights the recommended choice for new solutions.
After selecting the model:
- Follow the corresponding Get Started workflow from project creation through startup and initialization.
- Use Configuration for detailed package, authentication, API access, and data-access references.
- Use the ASP.NET Core MVC Integration guidance when maintaining an existing MVC-based integration.
Use the linked Configuration topics when you need package- or API-specific options beyond the setup workflow.