Edit

Share via

Breaking changes in .NET Aspire 9.1

  • Article

If you're migrating an app to .NET Aspire 9.1, 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 .NET Aspire 9.1.

Breaking changes

Title Type of change Introduced version
Default container image name and tag changed Behavioral change .NET Aspire 9.1
Cosmos DB hosting integration obsolete API and default managed identity support Source incompatible, behavioral change .NET Aspire 9.1
Azure Service Bus hosting integration obsolete APIs Source incompatible .NET Aspire 9.1
Azure Event Hubs hosting integration obsolete APIs Source incompatible .NET Aspire 9.1
IDistributedApplicationTestingBuilder API changes Binary incompatible .NET Aspire 9.1
Python hosting integration parameter name changes Source incompatible .NET Aspire 9.1