After my Aspire talk I got multiple questions. Two of them deserve some further explanation.
- How does Testcontainers relate to Aspire?
- And do Dev Containers solve the same problem?
Both involve containers, so the confusion is understandable. They solve different problems, though.
How does Testcontainers relate to Aspire?
Both tools start containers for your dependencies (a database, a message broker, a cache). The difference is when and for whom.
- Testcontainers is a library you call from your test code. It starts a container, waits until it’s ready, and throws it away when the test finishes.
- Aspire is an application model. In the AppHost you describe your services and their dependencies, and Aspire orchestrates them for your local dev loop, including service discovery, connection strings, telemetry and the dashboard.
With Testcontainers, the test owns the infrastructure:
var postgres = new PostgreSqlBuilder()
.WithImage("postgres:16")
.Build();
await postgres.StartAsync();
var connectionString = postgres.GetConnectionString();With Aspire, the AppHost owns it:
var builder = DistributedApplication.CreateBuilder(args);
var postgres = builder.AddPostgres("postgres");
var catalogDb = postgres.AddDatabase("catalogdb");
builder.AddProject<Projects.Catalog_Api>("catalog-api")
.WithReference(catalogDb)
.WaitFor(catalogDb);
builder.Build().Run();So the question becomes: do you need both? Often, yes.
Aspire also has its own testing support. With Aspire.Hosting.Testing you can start your entire AppHost from an integration test:
var appHost = await DistributedApplicationTestingBuilder
.CreateAsync<Projects.MyApp_AppHost>();
await using var app = await appHost.BuildAsync();
await app.StartAsync();
var httpClient = app.CreateHttpClient("catalog-api");
var response = await httpClient.GetAsync("/products");This tests the whole distributed application as you described it in the AppHost. Testcontainers is more focused. It’s a good fit when you want to test one component (a repository, a message handler) against a real dependency, without starting everything else.
A rough rule of thumb:
- Testcontainers: isolated tests of a single component against a real dependency.
- Aspire testing: end-to-end tests of the full application as modelled in your AppHost.
- Aspire AppHost: running the full application for development.
Remark: Aspire’s database and broker resources run on the same container runtime Testcontainers uses. They don’t compete with each other, and you can use both in the same solution.
Do Dev Containers solve the same problem?
No. Dev Containers solve the “works on my machine” problem for the development environment, not for the application’s dependencies.
A Dev Container (see containers.dev) defines the environment you code in: the SDK version, tools, extensions and settings. Everyone who opens the repo gets the same setup, whether in VS Code, GitHub Codespaces or another supporting tool.
- Dev Containers: where you develop. Your tooling is containerized.
- Aspire: what you run. Your app and its dependencies are modelled and orchestrated.
- Testcontainers: what your tests need. Dependencies are started on demand from test code.
They stack well. You can open your Aspire solution in a Dev Container so a new team member gets the right .NET SDK and tooling on day one. Aspire then starts the dependencies from inside that environment.
Remark: Running containers from inside a Dev Container (Aspire or Testcontainers) requires access to a container runtime. Check how your Dev Container reaches Docker (Docker-in-Docker or the host socket) before you assume it works.
Quick overview
| Solves | Scope | |
|---|---|---|
| Dev Containers | Consistent dev environment | Your tooling |
| Aspire | Orchestrating and observing your app locally | Your application |
| Testcontainers | Disposable dependencies in tests | Your tests |
That’s it!
More information

