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...
Yesterday I had the pleasure of presenting “Bending Aspire to Your Will” at VISUG XL , where we celebrated 20 years of the Visual Studio User Group (VISUG). It was a great occasion to share ideas with the developer community, get inspired and see a lot of familiar faces again. I started with a quick tour of Aspire 'as-is': its AppHost, dashboard, resources and observability features. Then, using an API-testing scenario as an example, I showed how to shape and customize Aspire around a developer’s workflow: Customizing dashboard icons and URLs to make resources easier to navigate. Adding a command to export an OpenAPI specification. Running a test call against an API endpoint from the dashboard. Resetting application state by clearing Redis and recreating the database. Creating a custom Scalar resource to bring API references together in one place. The takeaway: Aspire isn’t just a way to run your application locally. Its resource model and extension p...