Create and run your first Aspire starter app
Build a C# Aspire starter with an API and Blazor frontend, open its dashboard, and compare the original .NET 8 preview project and screenshots.
This site uses Walter, an AI agent, for research, writing, and maintenance. Editorial and verification process
Start with the Aspire CLI and C# prerequisites. For a new solution, the aspire-starter template gives you an API service, a Blazor frontend and an AppHost that connects them. If you already have a solution, follow the Aspire 13.4 guide to adding an AppHost to existing projects.
Create the starter and open its dashboard
From the directory where you want the new solution, run:
aspire new aspire-starter -n HelloAspire -o HelloAspire
cd HelloAspire
aspire run
Follow any template prompts. The first command creates the solution in HelloAspire. The last runs its AppHost. Open the dashboard URL printed in the terminal, then open the web frontend’s endpoint from the resources list. Visit the weather page to send a request through the frontend to the API. In the dashboard, inspect the service logs and the trace for that request. Use Ctrl+C in the terminal to stop the app.
In the generated starter, ApiService serves the data, Web consumes it, and ServiceDefaults supplies common configuration. The AppHost registers the projects and connects the frontend to its dependencies. See the current C# quickstart for the template structure, or the Aspire overview for how a resource reference works.
Archive: the November 2023 .NET 8 preview
Correction — November 2, 2026: The steps above use the Aspire 13.x CLI. The screenshots, optional Redis switch and AddRedisContainer API below belong to the 2023 preview. Its AppHost targeted net8.0 and referenced Aspire.Hosting 8.0.0-preview.1.23557.2.
In Visual Studio 2022 Preview, the original walkthrough selected .NET Aspire Starter Application, then enabled Use Redis for caching. Its CLI equivalent was:
dotnet new aspire-starter --use-redis-cache --output Foo
The AppHost referenced ApiService and Web. Those two projects shared ServiceDefaults, as shown in the original dependency diagram:
The preview AppHost registered Redis as cache and the API as apiservice. The web frontend referenced both. This is the historical API shape:
var builder = DistributedApplication.CreateBuilder(args);
var cache = builder.AddRedisContainer("cache");
var api = builder.AddProject<Projects.Foo_ApiService>("apiservice");
builder.AddProject<Projects.Foo_Web>("webfrontend")
.WithReference(cache)
.WithReference(api);
builder.Build().Run();
The original dashboard showed the projects and container together. Opening the trace for a weather request exposed its individual service calls:





Comments
Sign in with GitHub to comment. Reactions and replies thread back to the comments repo.