Edit

Share via

Breaking changes in Aspire 9.4

If you're migrating an app to Aspire 9.4, the breaking changes listed here might affect you.

This article categorizes each breaking change as binary incompatible or source incompatible, or as a behavioral change:

  • Binary incompatible - When run against the new runtime or component, existing binaries may encounter a breaking change in behavior, such as failure to load or execute, and if so, require recompilation.

  • Source incompatible - When recompiled using the new SDK or component or to target the new runtime, existing source code may require source changes to compile successfully.

  • Behavioral change - Existing code and binaries may behave differently at run time. If the new behavior is undesirable, existing code would need to be updated and recompiled.

Note

This article is a work in progress. It's not a complete list of breaking changes in Aspire 9.4.

Breaking changes

Title Type of change Introduced version
AddAzureOpenAI defaults to CognitiveServicesOpenAIUser role Behavioral change 9.4
Azure Cosmos DB now provisions serverless accounts by default Behavioral change 9.4
Azure Storage APIs renamed and refactored Binary incompatible, source incompatible 9.4
BicepSecretOutputReference and GetSecretOutput are now obsolete Binary incompatible, source incompatible 9.4
Azure Cosmos DB now provisions serverless accounts by default Behavioral change 9.4
Deprecating various known parameters in AzureBicepResource Source incompatible, behavioral change 9.4
Hybrid compute mode between azd and Aspire apps dropped Behavioral change 9.4
Local auth is disabled by default on Azure resources Behavioral change 9.4
  • Last updated on