Aspire 13.3 Simplifies Multi-Language Dev Environments

Chris Ayers announced the immediate release of Aspire 13.3 during his session at NDC Toronto. The new version introduces a suite of updated capabilities and tools aimed at enhancing the developer experience.

"today Aspire 13.3 dropped. So, a brand new version of Aspire dropped today," Ayers stated, marking a significant update to the platform.

Configuration settings are typically fragmented across various formats, including YAML, JSON, and application-specific settings files, leading to complexity. Furthermore, custom orchestration scripts, while common, are often difficult to maintain and prove unreliable over time.

Chris Ayers highlighted these frustrations, asking, "Like how many times do you have like eight terminal tabs or windows and you started this docker image and you copied the URL and the IP and then you paste it into this thing and then oh you guys had this environment variable."

Aspire aims to simplify this by making development tools 'agent aware,' which automatically correlates logs, spans, and metrics. This integration streamlines the process, enabling developers to effectively use OpenTelemetry for monitoring and debugging their applications in a local development environment.

"it's really hard to set up and use that locally like a lot of time. How are you able to use hotel properly on your local dev box on a regular basis?" Ayers noted, emphasizing the common struggles.

The Aspire CLI is responsible for managing tooling updates and the execution of projects, providing a command-line interface for various tasks.

The AppHost forms the core of Aspire, offering declarative service and dependency orchestration that automates how different components of an application interact. The Dashboard serves as a unified command center, presenting telemetry data, logs, and resource monitoring in a single, accessible interface.

Integrations allow for plug-and-play capabilities, providing pre-built components like Azure emulators and Redis caches, which can be easily added to projects. Chris Ayers summarized these, stating, "There is an Aspire CLI... The heart of Aspire that does a lot of what you need is in the apphost... The dashboard is the command center... And then the integrations are where we start plugging in capabilities."

The Aspire dashboard can operate independently without requiring the full Aspire orchestration suite. It runs as a memory-resident component, deployable as a standalone Docker image, which provides flexibility in its usage. This capability allows developers to use the dashboard as an OpenTelemetry interface for debugging or monitoring, even in environments where the complete Aspire platform is not implemented, reducing overhead.

"It's local. It's just in memory. So you can invoke a Docker image and use that dashboard. You can point your apps at the Inspire dashboard to use as an open telemetry interface," explained Chris Ayers.

This feature significantly reduces the need for manual configuration, as developers can rely on standard naming conventions for their services. The 'WithReference' method further simplifies this process by automatically managing dependency wiring, ensuring that services connect to each other seamlessly.

"All this stuff is just dynamically made on the fly and and wired together for me. So I don't even really need to set any of this," Chris Ayers explained, highlighting the efficiency gains.

Aspire automatically constructs a dependency graph, which enables it to order the startup of services logically. This ensures critical components, such as databases, are initiated before the API layers that depend on them, and API layers start before web frontends. The system also incorporates health checks to verify service availability and effectively manages cleanup processes upon application shutdown.

"if you're depending on something your front end depends on your back end your back end depends on a database it builds that graph so it knows I need to start medicine it's my database before I start my API layer," Chris Ayers noted, explaining the dependency management.

Initially focused on C#, Aspire has recently expanded its AppHost capabilities to include TypeScript. Looking ahead, support for Python, Java, and Go AppHosts is anticipated in the coming months. This expansion aims to establish a consistent development model across various programming languages, providing a unified experience for developers regardless of their preferred language.

"C# TypeScript they are supporting Python coming and Java and Go will all be available in as app hosts in the coming months or so," Chris Ayers confirmed, detailing the roadmap.

Aspire offers two main types of integrations: hosting integrations, which operate on the server side, and client-side integrations, exemplified by Aspire Redis. These integrations are designed to automatically manage naming conventions and inject connection strings, simplifying the setup process for developers.

Developers can explore the range of available integrations through the official Aspire documentation site, which provides comprehensive information on each component. Chris Ayers clarified the purpose of these integrations: "This is when I start up my application, I have a dependency of some kind that I need to spit up to reference."

By using commands like 'Aspire add Cosmos,' the tool automatically searches for and integrates the necessary components into the system. This includes pulling emulators as Docker images for local development environments, simplifying the setup and configuration of dependencies.

Chris Ayers demonstrated, "We've got our our Aspire CLI. We can add our component. We can add say Cosmos Aspire add. It's going to search for integrations. We have a ton of these."

Aspire uses dedicated config files to keep track of app host locations, ensuring that commands like 'Aspire run' or 'Aspire test' can be executed from any folder within the project. The CLI also provides robust support for managing secrets and environment variables, crucial for securing and customizing application behavior. Developers can audit their configurations using the 'config list' command, maintaining clear oversight of their project settings.

Chris Ayers pointed out, "all of this stuff you'll notice also has these little Aspire config files. These kind of keep track of like where your app host is. So no matter what folder you're in, you can do Aspire run or Aspire test."

This integration allows AI agents to invoke CLI commands, facilitating tasks such as checking resources, reading logs, and troubleshooting issues within the environment. Significantly, AI agents can also suggest solutions for dependency problems or configuration errors, further streamlining development.

Chris Ayers highlighted, "Now they also added this agent MCP command. So now I can with Visual Studio expired agent. This will let me manage my environment and set up an MCP."

Aspire's CLI now integrates AI-powered semantic search to address the common issue of AI models relying on outdated training data. This feature allows the CLI to retrieve the absolute latest, live documentation, ensuring developers always have access to current information. It also enables querying logs and dependencies with full context, enhancing troubleshooting and development efficiency.

Chris Ayers emphasized its benefit: "So it will search the latest docs. So we know the problems we have with AI models a lot of times is they're using old trained data... Spire Docs search cosmos like this gets the absolute latest documentation that's live."

This functionality is supported by the AppHost, which automates dependency installations such as 'npm install.' By automatically handling environment wiring, Aspire significantly reduces developer toil, making it easier to manage complex, multi-language projects.

"we can hit a debug point... it'll let us like step into the code, step out of the code across multiple languages," Chris Ayers demonstrated, showcasing the practical advantages.

This feature allows developers to configure persistent lifetimes and environment variables, simplifying infrastructure requirements across diverse deployment environments. The platform aims to reduce the manual effort involved in preparing applications for deployment.

Chris Ayers stated, "when we publish, we can publish container files. So if you have your um if you don't even have a Docker file, this will actually make a Docker file for you."

The platform supports local, identity-free development while also providing robust Role-Based Access Control (RBAC) for production environments. The primary objective is to minimize the toil associated with component wiring and configuration, offering a streamlined deployment experience.

Chris Ayers emphasized, "there is Kubernetes integration as well where you can have a Kubernetes environment added into your outpost and you can leverage help to deploy things out."