The .NET Aspire team clarified this change in terminology: We originally named these components because... well... they're components! But we've realized that it's such an overloaded term in development that we were actually just confusing people (and ourselves). Our documentation has been updated to reflect the change to Integrations and we will be using that terminology in our content moving forward.
In .NET Aspire 8.2, Integrations are utilized in two main ways. First, as a Hosting package that was added to the AppHost project, which simplifies launching resources and connecting them during local development. Second, as a package within the application code, this makes easier the process of connecting to resources created in the AppHost and simplifies the setup and configuration of new cloud services.
The release also includes improvements in testing procedures. The .NET Aspire team, with contributions from the community, has expanded its suite of tests to ensure that updates to Integrations do not disrupt existing applications. This enhancement aims to facilitate smoother version upgrades and minimize potential issues.
A significant breaking change in .NET Aspire 8.2 involves a known issue with building projects that reference version 8.1.0 when the 8.2.0 workload is installed. Users are advised to ensure their AppHost project references the latest version of the Aspire.Hosting.AppHost package by including the following line in the project file.
[
Collection
]
[
|
...
]