Skip to main content

Visug XL 2026 - Bending Aspire to your will - Q&A

 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

SolvesScope
Dev ContainersConsistent dev environmentYour tooling
AspireOrchestrating and observing your app locallyYour application
TestcontainersDisposable dependencies in testsYour tests

That’s it!

More information

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...