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(); a...