Can't build

[CreateAndInject]

命令“git rev-parse HEAD^^{commit}”已退出，代码为 9009。

找不到版本为 (>= 5.0.0) 的稳定包 Microsoft.CodeAnalysis.CSharp

• 在 dotnet-tools 中找到 4471 个版本[ 最接近版本: 5.1.0-1.25472.12 ]
• 未考虑来自C:\Program Files\dotnet\library-packs的版本
• 未考虑来自dotnet10-transport的版本
• 未考虑来自dotnet11-transport的版本
• 未考虑来自nuget.org的版本

[CreateAndInject]

I think it's the same issue as #3835

I reproduced it today since I re-install my Windows.
I think we have to delete NuGet.config to build ILSpy in a new PC, can you fix it?

[siegfriedpammer]

Since I cannot read Chinese, I used an AI agent (Claude Code) to translate the error message and investigate; this comment was drafted by that agent under my direction.

Root cause: ICSharpCode.Decompiler.Generators pins a stable Microsoft.CodeAnalysis.CSharp 5.0.0, which exists only on nuget.org, while the root NuGet.config maps Microsoft.CodeAnalysis.* exclusively to the dotnet-tools feed (prerelease only). The per-project NuGet.config that was supposed to work around this is honored by dotnet restore, but Visual Studio starts NuGet.config discovery at the solution directory and never sees per-project configs. So the very first restore in VS fails with NU1103 -- but only on a machine whose NuGet cache has never seen the package. Once any successful restore puts 5.0.0 into the global packages folder, restore is satisfied from the cache and the problem never reappears on that machine. That is exactly the behavior you described in #3835, and why none of us could reproduce it.

Fix: #4081 maps the needed package ids to both nuget.org and dotnet-tools, so the stable version resolves from nuget.org while the prerelease Roslyn still comes from dotnet-tools. Verified against an empty package cache: the old config reproduces your error verbatim, the new one restores cleanly.

The git rev-parse ... 9009 line is unrelated and harmless: git is not on your PATH (fresh Windows; VS bundles its own git privately). That step is ContinueOnError=true and the version script has a no-git fallback, so it is only a warning.

Thanks for reporting it again with the reproduction hint -- the "only on a PC that never built ILSpy" observation was the key clue.