C# and .NET apps
Use Aspire with C# projects, file-based apps, and other .NET workloads.
Start with C# file-based apps or Project resources.
Languages & runtimes
Цей контент ще не доступний вашою мовою.
Aspire works well with distributed apps that span more than one service, tool, or runtime. You can choose the AppHost style that fits your repo, then bring in the languages and frameworks your app already uses.
What this means in practice
Section titled “What this means in practice”- Write the AppHost in C# or TypeScript today.
- Orchestrate services and tools written in C#, JavaScript, Python, Go, Java, Rust, PowerShell, and more.
- Start with the Aspire Dashboard if observability is your first step.
- Adopt Aspire without rewriting your existing app around a single language.
Two choices to know
Section titled “Two choices to know”When people ask whether Aspire supports a language, they usually mean one of these two things:
- AppHost language: the language you use to define how your distributed app is wired together.
- App language or runtime: the language and runtime used by the services, frontends, workers, scripts, and tools inside that app.
For example, you might use a TypeScript AppHost to coordinate a Python worker, a Node.js frontend, and a C# API in the same application model.
AppHost languages
Section titled “AppHost languages”Both AppHost styles use the same Aspire model. The main difference is how the orchestration is authored and how it fits into your existing workflow.
| AppHost language | Good fit for | Start here | Support |
|---|---|---|---|
| C# | Teams already using .NET tooling or who want a single-file AppHost | What is the AppHost? | Official |
| TypeScript | Teams working in Node.js or TypeScript workspaces | TypeScript AppHost project structure | Official |
Guides for app languages and runtimes
Section titled “Guides for app languages and runtimes”Aspire can coordinate apps written in multiple languages. Some guides are best described by language (for example, C# or Python), while others cover a broader runtime or ecosystem (for example, .NET or Node.js).
The sections below use the labels that are most helpful when you’re trying to answer one practical question: “How do I use Aspire with the stack I already have?”
Official guides
Section titled “Official guides”JavaScript and Node.js apps
Use Aspire with JavaScript apps, Node.js services, and frontend workflows such as Vite.
Start with JavaScript integration and Standalone Aspire dashboard for Node.js.
Python apps
Use Aspire with Python services and OpenTelemetry-enabled Python apps.
Start with Python integration and Standalone Aspire dashboard for Python.
Community Toolkit guides
Section titled “Community Toolkit guides”Go apps
Add Go services through the Community Toolkit.
Start with Go integration.
Java apps
Add Java services through the Community Toolkit.
Start with Java integration.
Rust apps
Add Rust services through the Community Toolkit.
Start with Rust integration.
PowerShell scripts and tools
Add PowerShell-based scripts and developer tools through the Community Toolkit.
Start with PowerShell integration.
Dashboard guides for existing apps
Section titled “Dashboard guides for existing apps”If you want to start with observability before adopting a full AppHost, use a standalone dashboard guide: