Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
If you're migrating an app to .NET Aspire 9.3, 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.3.
Breaking changes
| Title | Type of change | Introduced version |
|---|---|---|
| AddAzureSqlServer assigns a dedicated user-assigned managed identity as the administrator | Behavioral change | 9.3 |
| Change the default SKU used for creating a new Azure SQL database | Behavioral change | 9.3 |
| Remove publisher APIs | Binary incompatible, source incompatible, and behavioral change | 9.3 |
| Http(s) health checks changes in .NET Aspire 9.3 | Binary and source incompatible | 9.3 |
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
.NET Aspire