Aspire cli `aspire add` does not support Central Package Management (13.0.0)

[zprobinson]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I'm not sure if this use case is covered in the development of fixes to #11655, but when I used aspire add to add the Aspire.Hosting.SqlServer::13.0.1 package to my AppHost, it results in the following csproj update (despite a Directory.Packages.props file existing at the root next to the .slnx file):

  <!-- project-name.AppHost.csproj -->
  <ItemGroup>
    <PackageReference Include="Aspire.Hosting.SqlServer" Version="13.0.1" />
  </ItemGroup>

Expected Behavior

I would expect that my Directory.Packages.props file is updated to include the following:

    <PackageVersion Include="Aspire.Hosting.SqlServer" Version="13.0.1" />

and my project-name.AppHost.csproj file is updated to include the following:

    <PackageReference Include="Aspire.Hosting.SqlServer" />

Steps To Reproduce

1. Create a new solution via dotnet new sln
2. Migrate to slnx file via dotnet sln migrate
3. Create a new project via dotnet new aspire and add to solution
4. [prob not relevant, but what I was doing] Create new webapi project via dotnet new webapi and add to both solution and AppHost
5. Build out Directory.Packages.props file and fix up the web api and ServiceDefaults to comply
6. Use aspire cli to add Aspire.Hosting.SqlServer::13.0.1 to aspire project

Exceptions (if any)

No response

.NET Version info

.NET SDK:
 Version:           10.0.100
 Commit:            b0f34d51fc
 Workload version:  10.0.100-manifests.355811b7
 MSBuild version:   18.0.2+b0f34d51f

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22631
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\10.0.100\

.NET workloads installed:
There are no installed workloads to display.
Configured to use workload sets when installing new manifests.
No workload sets are installed. Run "dotnet workload restore" to install a workload set.

Host:
  Version:      10.0.0
  Architecture: x64
  Commit:       b0f34d51fc

.NET SDKs installed:
  9.0.305 [C:\Program Files\dotnet\sdk]
  10.0.100 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 8.0.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 8.0.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 10.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 10.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 8.0.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 9.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 9.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 10.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  x86   [C:\Program Files (x86)\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
  Not set

global.json file:
  Not found

Anything else?

My aspire cli is 13.0.0, but I had ran aspire update --self earlier in the day (downloading 13.0.1) but hadn't updated the PATH yet (so 13.0.0 was the version in use).

[davidfowl]

What version of the .NET SDK are you using?

[zprobinson]

What version of the .NET SDK are you using?

dotnet --version
10.0.100

[adis-dizdarevic]

I had the same issue. Removing the three "default" packages (Aspire.Dashboard.Sdk.win-x64, Aspire.Hosting.AppHost, Aspire.Hosting.Orchestration.win-x64) and relying on the Aspire AppHost SDK fixed the issue for me. See my current csproj:

<Project Sdk="Aspire.AppHost.Sdk/13.1.0">

    <PropertyGroup>
        <OutputType>Exe</OutputType>
        <TargetFramework>net10.0</TargetFramework>
        <ImplicitUsings>enable</ImplicitUsings>
        <Nullable>enable</Nullable>
    </PropertyGroup>

</Project>

After that, I could add other packages via CPM.

[austinw-fineart]

Basically the migration removed the PackageReference from the AppHost csproj but failed to do the same for the corresponding PackageVersion in Directory.Packages.props. The existence of the PackageVersion would conflict with the PackageReference that Aspire.AppHost.Sdk includes.

[mip1983]

Just to add, it's similarly problematic if you use aspire update, it changes the AppHost in a breaking way

[davidfowl]

This is fixed in the next version (the original issue).

[davidfowl]

@mip1983 open a new issue plz