Aspire 13 Delivers Multi-Language Support and Significant Enhancements Across the Platform

Aspire 13 repositions Aspire as a full polyglot application platform and removes the .NET-specific branding. Version 13 delivers first-class support for Python and JavaScript alongside existing .NET capabilities. Python support enables running scripts, modules, and virtual-environment executables and includes dedicated Uvicorn integration for ASGI frameworks. Aspire automatically configures endpoints, command-line arguments, and development-time reload features. Builder APIs allow adding Python apps, modules, and executables with example usage provided. Package management auto-detects pip, uv, or virtual environments and generates production Dockerfiles. JavaScript support introduces AddJavaScriptApp, unified package-manager detection, automatic script execution, container-based build pipelines, and specialized Vite handling with optimized builds and hot module replacement.

"Aspire 13 has been released as a major milestone in the platform's evolution. As reported by the team, Aspire is no longer branded as ".NET Aspire" and is now positioned as a full polyglot application platform. According to the announcement, version 13 brings first-class support for Python and JavaScript alongside existing .NET capabilities, marking a significant shift toward multi-language development, debugging, and deployment workflows."

"var builder = DistributedApplication.CreateBuilder(args); // Run a Python script directly var etl = builder.AddPythonApp("etl-job", "../etl", "process_data.py"); // Run a Python module (python -m celery) var worker = builder.AddPythonModule("celery-worker", "../worker", "celery") .WithArgs("worker", "-A", "tasks", "--loglevel=info"); // Run an executable from the virtual environment (e.g., gunicorn) var api = builder.AddPythonExecutable("api", "../api", "gunicorn") .WithArgs("app:app", "--bind", "0.0.0.0:8000"); Package management is handled by automatically detecting pip, uv, or virtual environments, also production Dockerfiles are generated based on the project configuration."

Read at InfoQ