.NET Aspire 9.0 - GA Release content

[IEvangelist]

Summary

.NET Aspire 9.0 - GA Release content.

• Fixes Upgrade snippet projects to .NET Aspire 9.0 #1993
• Fixes Create content for custom resource commands #2014
• Fixes Poor documentation #1818
• Fixes Context into the Weather API #2004
• Fixes Document Entra ID and new Azure API pattern for Redis, PostgreSQL, and SQLServer #1704
• Fixes [Breaking change]: Ollama integration updates #2009
• Fixes [New article]: WaitFor/WaitForCompletion docs #1556
• Fixes Azure Local Provisioning needs az CLI installed #2003
• Fixes Document Azure resource naming breaking change #1666
• Fixes Document the workload-related changes in .NET Aspire 9.0 #1667
• Fixes [New article]: Aspire + Azure Functions integration #1706
• Fixes Networking mentions service bindings (which were the original name for endpoints) #1823
• Fixes Add IDistributedApplicationLifecycleHook docs #1613
• Fixes Start/stop/restart for 9.0 #1662
• Fixes .NET Aspire SDK - article #1888
• Fixes [New article]: Update to .NET Aspire 9 #1859
• Fixes Add a link to the .NET Aspire support policy #1882
• Fixes [New article]: Conceptual docs for new eventing API #1478
• Fixes Update template docs for 9.0 GA changes #1869
• Fixes Document 9.0 breaking changes #1868
• Fixes [WebtoolsE2E] [Multiple docs] The .NET Aspire Orchestrator Support dialog screenshot needs to be updated because the Aspire Version displayed. #2026
• Fixes [WebtoolsE2E] [Configure the API with distributed caching] The documentation should be updated to add the 'using' required by the code. #2027
• Fixes [WebToolsE2E][Dashboard] Some more updates are needed in "Explore the .NET Aspire dashboard" using VS/CLI with aspire. #2022
• Fixes [WebToolsE2E] [Multiple docs] The Dashboard screenshot needs to be updated because the Endpoint of the ApiService does not contain "/weatherforecast" in Aspire 9.0.0 #2016
• Fixes [WebToolsE2E] Can't clear the content in home page when do scenario Tutorial: Connect an ASP.NET Core app to .NET Aspire storage components. #2024
• Fixes [WebToolsE2E][Multiple docs] Some instructions need to be updated in "Tutorial: Deploy a .NET Aspire project with a SQL Server Database to Azure" #2017

---

Internal previews

Toggle expand/collapse

📄 File	🔗 Preview link
docs/caching/caching-integrations-deployment.md	Tutorial: Deploy a .NET Aspire project with a Redis Cache to Azure
docs/caching/caching-integrations.md	Implement caching with .NET Aspire integrations
docs/caching/stackexchange-redis-distributed-caching-integration.md	[.NET Aspire Redis®* distributed caching integration](https://review.learn.microsoft.com/en-us/dotnet/aspire/caching/stackexchange-redis-distributed-caching-integration?branch=pr-en-us-1867)
docs/caching/stackexchange-redis-integration.md	docs/caching/stackexchange-redis-integration
docs/caching/stackexchange-redis-output-caching-integration.md	[.NET Aspire Redis®* output caching integration](https://review.learn.microsoft.com/en-us/dotnet/aspire/caching/stackexchange-redis-output-caching-integration?branch=pr-en-us-1867)
docs/community-toolkit/overview.md	Overview
docs/database/postgresql-integration.md	.NET Aspire PostgreSQL integration
docs/deployment/manifest-format.md	docs/deployment/manifest-format
docs/extensibility/custom-hosting-integration.md	Create custom .NET Aspire hosting integrations
docs/frameworks/orleans.md	Use Orleans with .NET Aspire
docs/fundamentals/app-host-overview.md	.NET Aspire orchestration overview
docs/fundamentals/dashboard/enable-browser-telemetry.md	docs/fundamentals/dashboard/enable-browser-telemetry
docs/fundamentals/dashboard/explore.md	Explore the .NET Aspire dashboard
docs/fundamentals/dashboard/overview.md	.NET Aspire dashboard overview
docs/fundamentals/external-parameters.md	External parameters
docs/fundamentals/networking-overview.md	docs/fundamentals/networking-overview
docs/fundamentals/persist-data-volumes.md	Persist .NET Aspire project data using volumes
docs/fundamentals/service-defaults.md	.NET Aspire service defaults
docs/fundamentals/setup-tooling.md	.NET Aspire setup and tooling
docs/get-started/add-aspire-existing-app.md	Tutorial: Add .NET Aspire to an existing .NET app
docs/get-started/aspire-overview.md	docs/get-started/aspire-overview
docs/get-started/build-aspire-apps-with-nodejs.md	Orchestrate Node.js apps in .NET Aspire
docs/get-started/build-aspire-apps-with-python.md	Orchestrate Python apps in .NET Aspire
docs/get-started/build-your-first-aspire-app.md	Quickstart: Build your first .NET Aspire solution
docs/index.yml	docs/index
docs/reference/aspire-faq.yml	Frequently asked questions about .NET Aspire
docs/testing/write-your-first-test.md	Write your first .NET Aspire test
docs/toc.yml	docs/toc
docs/whats-new/index.yml	.NET Aspire — what's new?
docs/whats-new/toc.yml	docs/whats-new/toc

Note

This table shows preview links for the 30 files with the most changes. For preview links for other files in this PR, select OpenPublishing.Build Details within checks.

[davidfowl]

The placement of the azure content within the integration package seems to prominent. I think we should push all of the azure content in redis and postgres to the bottom of the page. Later we can move it to it's own page. There's APIs to document there that are not related to postgres.

[IEvangelist]

The placement of the azure content within the integration package seems to prominent. I think we should push all of the azure content in redis and postgres to the bottom of the page.

It's at (or near) the bottom of each respective section. At the bottom of the hosting integration section, there's the Azure hosting alterative. For the client integration section, it's under the standard registration, but before the keyed approach. I could move it below keyed registration.

Later we can move it to it's own page.

Sounds good. We could have a zone pivot for "Azure Cache", then it's an explicit selection by the reader, thoughts on that?

There's APIs to document there that are not related to postgres.

What APIs are you specifically referring to? Are they needed for .NET Aspire 9.0, are there related issues?

[davidfowl]

It's at (or near) the bottom of each respective section. At the bottom of the hosting integration section, there's the Azure hosting alterative. For the client integration section, it's under the standard registration, but before the keyed approach. I could move it below keyed registration.

I think it should be at the very bottom of the whole doc.

What APIs are you specifically referring to? Are they needed for .NET Aspire 9.0, are there related issues?

1. How to use AzureResources with an emulator locally
2. Using the Azure.Provisioning APIs to change common properties (like the sku etc)

[IEvangelist]

I think it should be at the very bottom of the whole doc.

Done. All the Redis and PostgreSQL integration articles are updated as such.

How to use AzureResources with an emulator locally

This one #1560?

Using the Azure.Provisioning APIs to change common properties (like the sku etc)

Something like these APIs dotnet/aspire-samples#531?

[davidfowl]

This one #1560?

Yep. We need to rewrite the azure integration docs and they need to spell out the emulators and how to customize (using the Azure.Provisioning package).

Something like these APIs dotnet/aspire-samples#531?

Yep.

[IEvangelist]

Note

❌ The Snippets 5000 / snippets-build is failing ☹️

This is fully expected as we're pulling directly from the public 📦 NuGet feed, not from any private feed. Since we're pointing to net9.0 assets, we're blocked until all packages have been published and indexed on NuGet, and can be ingested by this CI job successfully. 🤓

• We will ship ASAP .
• Thank you for your patience! 🙏
• Made with all the love for the .NET community... 💜

[davidfowl]

The manifest schema should document the manifest types not the resource types (azure.bicep.v0 vs AddAzurePostgres). We can do this as a general improvement to the docs.

[joperezr]

This is fully expected as we're pulling directly from the public 📦 NuGet feed, not from any private feed. Since we're pointing to net9.0 assets, we're blocked until all packages have been published and indexed on NuGet, and can be ingested by this CI job successfully.

I see, I will let you know as soon as packages are up so you can go ahead and re-run and merge.