[SQLProjects] NuGet restore loop with centrally managed packages

[codijk]

Describe the bug

When updating the CommunityToolkit.Aspire.Hosting.SqlDatabaseProjects package in a Directory.Packages.props file, Visual Studio gets in a nuget restore loop.

A minimal reproduction has been created, which can be found here:
AspireNuGetLoop.zip

Regression

9.9.0 with .NET 9

Steps to reproduce

1. Open the provided solution
2. See the nuget restore loop happen.
3. Move from centrally managed packages to defining them in the CSPROJ directly.
4. Notice that the restore and build succeed.

Expected behavior

Works the same as when not using a Directory.Packages.props file.

Screenshots

IDE and version

Other

IDE version

VS 2026

Nuget packages

CommunityToolkit.Aspire.Hosting.SqlDatabaseProjects (13.0.0)

Additional context

No response

Help us help you

No, just wanted to report this

[codijk]

I think it goes wrong in this file.

[SamuelMcAravey]

@codijk I'm running into the same problem, same version of Visual Studio, and I get build errors complaining about the version of Microsoft.Build, which seems to be pulled in from that same file you indicated. VS 2026 seems to want version 18, and this library is forcing version 17.

I don't have a fix yet other than removing the reference which isn't great.

[ErikEJ]

@SamuelMcAravey That does not sound like the same issue. What makes you think it is?

If not, please create a new one.

[SamuelMcAravey]

@ErikEJ Apologies, I should have explained it a bit better.

I get the exact same NuGet restore loop error. I just get an extra error talking about the Microsoft.Build package, and those three packages @codijk mentioned (Microsoft.Build, Microsoft.Build.Framework, Microsoft.NET.StringTools) happen to be the packages which get stuck in the loop of restored, removed, restored again. I can see it flicking in and out in Visual Studio, and after it does that a few times I ultimately get the NuGet loop error. That's why I'm thinking it's the same problem, but if they really are different then I'm happy to open a separate issue. Thanks!

[ErikEJ]

@SamuelMcAravey Thanks for the additional explanation

[codijk]

@SamuelMcAravey that is exactly what I am seeing as well. Those 3 packages keep being added and removed until the NuGet restore loop error appears.

[pheeblyboos]

I also have exactly the same problem with Aspire projects and this package as described above by @codijk and @SamuelMcAravey using central package management. My VS gets stuck into a loop trying to restore the packages which fails on this project's package and then I get this error.
It is very blocking for upgrading to .NET 10, I have not been able to find a workaround for this. Trying different package versions together or pinning versions in our own project has not resolved this.

[ErikEJ]

@pheeblyboos
Workaround:

<ManagePackageVersionsCentrally>false</ManagePackageVersionsCentrally>

@aaronpowell Any ideas how to fix this?

[aaronpowell]

I don't think there's anything we can do in the toolkit to resolve it. My assumption is that it's related to the hack from #949 (comment) that is because the DacFx package is not doing the right thing with the MS Build libraries.

I'm not sure what to do about it short of trying to find the owners internally at MS

[ErikEJ]

@aaronpowell You mean the owners of the DacFX package?

[ErikEJ]

@dzsquared It sounds like @aaronpowell has soem ideas how you can fix this in the DacFX package

[aaronpowell]

Oh, I haven't an idea on how to fix it, just that that package is causing the MS Build assembly to be in the output folder which it shouldn't do

[ErikEJ]

@aaronpowell I misunderstood your comment here then: #949 (comment)

[Odonno]

Adding a Microsoft.Build reference to the SQL project seems to do the trick.

[ErikEJ]

@Odonno What does that reference look like?