Skip to content
← All solutions
ASP.NET Core logo

Frameworks solution

Run ASP.NET Core Locally with FlyEnv

ASP.NET Core projects use the .NET runtime with project-specific data services and a local reverse proxy. FlyEnv coordinates this cross-platform local web stack.

Local project stack

Services FlyEnv can manage around ASP.NET Core

About ASP.NET Core

ASP.NET Core is the cross-platform .NET framework for HTTP APIs and server-rendered web applications. It combines a hosting model, middleware pipeline, dependency injection, configuration providers, and web stacks such as Minimal APIs, MVC, Razor Pages, and SignalR.

Development generally uses the project SDK through `dotnet run` or an IDE launch profile. Local configuration can select Kestrel certificates, Entity Framework Core migrations, user secrets, and only those backing services such as SQL Server, PostgreSQL, Redis, or a message broker that the application actually configures.

Core capabilities

  • Minimal APIs
  • MVC and Razor Pages
  • Built-in dependency injection
  • Middleware pipeline
  • ASP.NET Core Identity
  • SignalR

Common use cases

  • Line-of-business web applications
  • REST and gRPC services
  • Real-time dashboards
  • Cross-platform enterprise APIs

An ASP.NET Core project is shaped by its launch profile

The .NET SDK and Kestrel can be enough for a small application; persistent data and distributed features add selected services.

.NET SDK and Kestrel
Builds and runs the application through `dotnet run` with development settings.
EF Core database
SQL Server, PostgreSQL, or another provider is used when the project applies migrations and stores application state.
Development HTTPS and secrets
The local development certificate and Secret Manager support secure browser flows without placing credentials in source control.

Project resources

For installation commands, supported versions, and project-specific configuration, refer to the official ASP.NET Core documentation.

Typical local stack

The exact services depend on the project, its release, and its local configuration. This is a common local setup, not a fixed requirement.

ComponentTypical role
.NETRuns the ASP.NET Core application.
PostgreSQLMySQLStores application data.
RedisMay support cache and distributed services.
NginxCaddyMay proxy a local application domain.

How FlyEnv helps

  • Select the project .NET runtime

    Match the SDK and runtime to the application.

  • Start selected services

    Keep the configured database and Redis local.

  • Use HTTPS locally

    Test browser, cookie, and API integrations securely.

Set up the local environment

Project installation stays with the upstream documentation. FlyEnv manages the runtimes, databases, web servers, and supporting services around it.

  1. 1Restore and run the project using its .NET instructions.
  2. 2Select the required .NET SDK or runtime.
  3. 3Start the configured database and Redis services.
  4. 4Configure a local domain and HTTPS when useful.

Ready to run ASP.NET Core locally?

Use FlyEnv to manage the runtimes, databases, web servers, and services around your local ASP.NET Core environment.

Download FlyEnv

Have questions using FlyEnv?