Remove Aspire CLI Native AOT workarounds for NuGet's Newtonsoft.Json dependency

[eerhardt]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

#19847 moved bundled NuGet operations into the Native AOT aspire CLI. NuGet.Client 7.12.0-rc.25, which the CLI now consumes, still reaches Newtonsoft.Json on some paths, so src/Aspire.Cli/Aspire.Cli.csproj carries temporary workarounds to keep the Native AOT publish clean:

• RuntimeHostConfigurationOption items that disable Newtonsoft's Newtonsoft.Json.Linq.JToken.SerializationIsSupported, ComponentModelIsSupported, and DynamicIsSupported feature switches.
• The ConfigureTrimming target, which collapses the remaining dynamic-dispatch warnings from Microsoft.CSharp and System.Linq.Expressions to one warning per assembly.
• IL2104;IL3053 in NoWarn, which suppresses those collapsed single-warn diagnostics.

These are only needed until NuGet removes its Newtonsoft.Json dependency from the code paths the CLI uses. Upstream that work is NuGet/NuGet.Client#7601.

The Newtonsoft switches also make the disabled code paths throw NotSupportedException at runtime, so any NuGet update that starts reaching one of them would fail at runtime rather than at publish time.

Describe the solution you'd like

Once NuGet/NuGet.Client#7601 ships in a NuGet.Client release:

1. Update NuGetPackageVersionForCli in eng/Versions.props to that release.
2. Remove the three Newtonsoft RuntimeHostConfigurationOption items, the ConfigureTrimming target, and IL2104;IL3053 from NoWarn in src/Aspire.Cli/Aspire.Cli.csproj.
3. Confirm a fresh Native AOT publish of Aspire.Cli reports no IL trim/AOT diagnostics without them. ILC is incremental, so delete artifacts/obj/Aspire.Cli/<config>/<tfm>/<rid>/native first or a repeat publish can report zero diagnostics without recompiling.

NuGet.UseSystemTextJsonDeserialization may still be required after that change; keep or remove it based on NuGet's AOT guidance at the time.

Additional context

Tracked for 14.0 so the workarounds are not left in place after the upstream fix ships.

[joperezr]

🤖 Aspire triage pass — 2026-09-23 02:01 UTC

Area: area-cli
Kind: feature-request
Repro: none — this tracks removal of temporary compatibility workarounds after an upstream dependency change
Affected version(s): not specified (latest: 13.5.4)
Severity: S4 — deferred maintenance with no current customer-facing failure

Urgency: ⚪ backlog — no milestone
Reason: actionable cleanup is blocked on an upstream release and is not important enough for the 13.6 train

Suggested owner(s): Ankit Jain (@radical) (score 69), backup David Pine (@IEvangelist) (score 21)
Evidence:

• radical merged fix(team-app): Watch Aspire 1P’s Proxima repository #20192, test(ci): enforce selective test trigger dependencies #19926, ci: Run extension and CLI E2E only for actual consumers #19882 in area-cli within the last 30 days
• radical closed [automated] Fix main CI failures being filed as PR infrastructure issues #19454, Labeller Job Failing #20277, Identify firewall rules for on-demand Copilot builds and tests #19908 as completed in area-cli
• IEvangelist merged Fix PR documentation workflow inputs and completion #20293, Modernize agentic workflows with gh-aw v0.88.7 #20209, Fix docs safe-output base fallback #19465 in area-cli within the last 30 days

Confidence: high
Needs human?: no