Aspire 13 is a surprisingly good way to make a mixed-stack project feel like one product instead of three separate repos held together by docs and duct tape. In this session, we’ll build a small polyglot system from scratch where a .NET API, a Python worker, and a Node front end all run under a single Aspire AppHost. The payoff is a clean, repeatable workflow for wiring services together, running them locally, and keeping configuration and dependencies from turning into everyone’s least favorite onboarding ritual.

As we grow the app, we’ll tackle the practical stuff that tends to break first in real teams. You’ll see how to add and connect services safely, manage environment configuration without guesswork, and make debugging across languages feel routine. We’ll also talk about the common failure patterns in polyglot systems, like mismatched dependency versions, “it only works on my machine” scripts, and hidden runtime assumptions, plus how Aspire helps you replace those with something intentional.

Finally, we’ll zoom out and connect the dots to the broader toolchain. We’ll look at the Aspire CLI and integrations that keep the workflow consistent as the system grows, what “production-ready” looks like in a polyglot repo, and how Aspire’s model maps to the way teams automate builds and deployments in CI. If you’re thinking about Azure, we’ll also talk through the kinds of infrastructure decisions teams typically want to control, and where Aspire can plug into that story.

You will learn:

• Aspire
• Integration
• CLI and Tooling