Getting Started
Use this section to choose an application model and complete the minimum setup for a working RecroGrid Framework application.
An application model defines how the browser-facing UI, authentication, API access, and RecroGrid Framework server runtime are divided between deployed applications. Make this decision before following a setup workflow because it determines the solution structure, authentication flow, and API boundary.
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.
Start with the recommended model
For a new application, start with the Server-side Application model.
From a deployment perspective, it consists of two applications:
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.
Choose an application model
| Model | Deployment shape | Use it when |
|---|---|---|
| Server-side Application | Blazor host + backend API application | You are starting a new application and want host-managed authentication and API access. |
| Blazor WebAssembly Application | Standalone WebAssembly client + backend API application | The browser must authenticate and call the backend API directly, or you maintain an existing direct-access client. |
| ASP.NET Core MVC | One integrated MVC application | You only need legacy configuration guidance for an existing MVC integration. This model is not recommended for new applications. |
For the complete deployment, development, authentication, and request-flow comparison, see Application Models.
Follow the documentation path
- Review Application Models and select the topology that fits your application.
- Follow either the Server-side Application or Blazor WebAssembly Application workflow from application creation through startup.
- Use Configuration for detailed package, authentication, API access, and data-access references.
- Use the legacy ASP.NET Core MVC Integration page only when you maintain an existing MVC-based integration.
The workflow pages provide the shortest path to a running application. Detailed package- and API-specific instructions remain in their canonical technical documentation and are linked from the relevant workflow step.