Add support for systems running only .NET 10.0 (without .NET 8.0 or 9.0) in Refitter.MSBuild

[christianhelle]

Fixes #881

Summary by CodeRabbit

• New Features

  • Detects .NET 10 runtimes and automatically selects matching runtime artifacts.

• New Packaging

  • Includes .NET 10 artifacts in MSBuild packaging and distribution.

• Tests

  • Test project target moved to .NET 10 and related resilience test packages removed.
  • Test run configuration changed to Release.

• Chores

  • CI workflow simplified by removing explicit SDK setup and minor workflow cleanups.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds .NET 10 support across packaging, runtime selection, tests, and CI: packages net10.0 artifacts, updates RefitterGenerateTask to prefer .NET 10, retargets tests to net10.0, and removes the explicit setup-dotnet step from the workflow.

Changes

Cohort / File(s)	Summary
MSBuild Project Packaging src/Refitter.MSBuild/Refitter.MSBuild.csproj	Added Content Include to package ../Refitter/bin/$(Configuration)/net10.0/**/* into tasks/net10.0 alongside existing net8.0 and net9.0 entries.
Runtime Selection Logic src/Refitter.MSBuild/RefitterGenerateTask.cs	Reordered detection to check for Microsoft.NETCore.App 10.x first; selects net10.0/refitter.dll and emits a diagnostic log when detected; retains net9.0 and net8.0 fallbacks.
Tests Target Framework test/MSBuild/Refitter.MSBuild.Tests.csproj	Updated TargetFramework from net8.0 → net10.0; removed several resilience-related package references.
CI Workflow / Build Script .github/workflows/msbuild.yml, test/MSBuild/build.ps1	Removed actions/setup-dotnet@v5 and its dotnet-version inputs from workflow; changed test build run to -c Release; minor whitespace/logging normalization.

Sequence Diagram(s)

mermaid
sequenceDiagram
rect rgba(200,200,255,0.5)
participant MSBuildTask as MSBuild Task
participant Runtime as .NET Host/Runtime
participant Files as Artifacts / FileSystem
participant Logger as Logger
end
MSBuildTask->>Runtime: Probe installed runtimes (query Microsoft.NETCore.App)
Runtime-->>MSBuildTask: Report versions (e.g., 10.x, 9.x, 8.x)
MSBuildTask->>Logger: Log detected runtime (prefer 10.x if present)
MSBuildTask->>Files: Select DLL path (tasks/net10.0/refitter.dll) or fallback
Files-->>MSBuildTask: Provide selected DLL for task execution
MSBuildTask->>Logger: Emit final selection diagnostic

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Fix MSBuild task so that the generated code is included in the compilation #745 — Modifies RefitterGenerateTask.cs behavior (GeneratedFiles / generation), touching the same task implementation.
• Add .NET 10 support #822 — Also adds .NET 10 support and adjusts packaging/workflow changes across the repo.
• Add support for systems running only .NET 9.0 (without .NET 8.0) in Refitter.MSBuild #746 — Prior addition of net9.0 support; similar packaging and runtime-selection changes.

Suggested labels

CI/CD

Poem

🐰 I sniffed the runtimes, found ten at play,
I packed new bins and hopped away.
Tests retargeted, CI trimmed the net,
A tiny hop forward—no build upset.
🥕 Puff of fur, and off we get!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly matches the primary change: adding .NET 10 support to Refitter.MSBuild for systems without earlier SDK versions.
Linked Issues check	✅ Passed	Changes implement .NET 10 support across build configuration (csproj), task selection logic (RefitterGenerateTask.cs), and CI/test infrastructure, fulfilling issue #881 requirements.
Out of Scope Changes check	✅ Passed	All changes align with .NET 10 support goal: packaging artifacts, runtime detection, test targeting, workflow updates, and build configuration are all directly related.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR adds support for .NET 10 runtime in Refitter.MSBuild by updating the runtime detection logic and package configuration. The changes enable the MSBuild task to detect and use the .NET 10 version of the Refitter tool when available.

Changes:

• Updated runtime detection to check for .NET 10 and select the appropriate Refitter DLL
• Added .NET 10 binaries to the MSBuild package content
• Updated test project to target .NET 10

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
src/Refitter.MSBuild/RefitterGenerateTask.cs	Added .NET 10 runtime detection and DLL path selection logic
src/Refitter.MSBuild/Refitter.MSBuild.csproj	Included .NET 10 binaries in the MSBuild package
test/MSBuild/Refitter.MSBuild.Tests.csproj	Updated target framework from net8.0 to net10.0

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 51.92%. Comparing base (4672538) to head (aa833f3).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #882   +/-   ##
=======================================
  Coverage   51.92%   51.92%           
=======================================
  Files          23       23           
  Lines        1610     1610           
=======================================
  Hits          836      836           
  Misses        755      755           
  Partials       19       19           

Flag	Coverage Δ
unittests	51.92% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@test/MSBuild/Refitter.MSBuild.Tests.csproj`:
- Around line 11-15: Pin the conflicting Microsoft.Extensions.* packages by
adding explicit PackageReference entries for
Microsoft.Extensions.Configuration.Abstractions,
Microsoft.Extensions.DependencyInjection.Abstractions, and
Microsoft.Extensions.Options set to version 10.0.2 (to match the
Microsoft.Extensions.Http 10.x graph) so the project-local references override
the transitive downgrade from Refit.HttpClientFactory 9.0.2; update the project
file to include these three package references
(Microsoft.Extensions.Configuration.Abstractions,
Microsoft.Extensions.DependencyInjection.Abstractions,
Microsoft.Extensions.Options) at version 10.0.2.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

# First, find the test project file and examine its structure
find . -name "Refitter.MSBuild.Tests.csproj" -type f

Repository: christianhelle/refitter

Length of output: 111

---

🏁 Script executed:

# Check for Directory.Packages.props (central package management)
find . -name "Directory.Packages.props" -type f

Repository: christianhelle/refitter

Length of output: 49

---

🏁 Script executed:

# Also check for any global package configuration
find . -name "*.props" -o -name "*.targets" | grep -i "package\|version" | head -20

Repository: christianhelle/refitter

Length of output: 49

---

🏁 Script executed:

# Explore the repository structure
git ls-files | grep -E "\.(csproj|props)$" | head -30

Repository: christianhelle/refitter

Length of output: 1307

---

🏁 Script executed:

# Examine the test project file
cat -n ./test/MSBuild/Refitter.MSBuild.Tests.csproj

Repository: christianhelle/refitter

Length of output: 880

---

🏁 Script executed:

# Check for Directory.Build.props files in relevant paths
find ./test/MSBuild -name "*.props" -o -name "*.targets"
find ./test -maxdepth 1 -name "Directory.*.props"
ls -la ./test/MSBuild/

Repository: christianhelle/refitter

Length of output: 501

---

🏁 Script executed:

# Check the root Directory.Build.props if it exists
ls -la ./Directory.Build.props 2>/dev/null || echo "No root Directory.Build.props"
cat -n ./src/Directory.Build.props 2>/dev/null | head -50

Repository: christianhelle/refitter

Length of output: 2006

---

🏁 Script executed:

# Check if there's any build log or error information in the repo
find . -name "*.log" -o -name "*build*" -type f | grep -i "test\|msbuild" | head -20

Repository: christianhelle/refitter

Length of output: 219

---

🏁 Script executed:

# Look for any GitHub Actions workflow or CI config that might show the NU1605 error
find . -name "*.yml" -o -name "*.yaml" | xargs grep -l "NU1605\|Microsoft.Extensions" 2>/dev/null | head -5

Repository: christianhelle/refitter

Length of output: 49

---

🌐 Web query:

Refit.HttpClientFactory 9.0.2 dependencies Microsoft.Extensions

💡 Result:

Refit.HttpClientFactory 9.0.2 depends on Microsoft.Extensions.Http (>= 9.0.3) for its supported targets (.NETStandard2.0, .NETFramework4.6.2, net8.0, net9.0, net10.0). [1][2]

Sources:

• NuGet package page for Refit.HttpClientFactory 9.0.2. [1]
• NuGet summary listing (Refit.HttpClientFactory dependencies). [2]

---

🌐 Web query:

Microsoft.Extensions.Http.Polly 10.0.2 dependencies

💡 Result:

Microsoft.Extensions.Http.Polly 10.0.2 direct package dependencies:

• Microsoft.Extensions.Http (>= 10.0.2). [1]
• Polly (>= 7.2.4). [1]
• Polly.Extensions.Http (>= 3.0.0). [1]

Source: NuGet package metadata for Microsoft.Extensions.Http.Polly 10.0.2. [1]

---

🌐 Web query:

Microsoft.Extensions.Http.Resilience 10.2.0 dependencies Microsoft.Extensions.Configuration.Abstractions DependencyInjection.Abstractions

💡 Result:

Short answer: No — Microsoft.Extensions.Http.Resilience 10.2.0 does not list Microsoft.Extensions.Configuration.Abstractions or Microsoft.Extensions.DependencyInjection.Abstractions as direct package dependencies. Its NuGet dependency list shows packages like Microsoft.Extensions.Diagnostics.ExceptionSummarization, Microsoft.Extensions.Telemetry.Abstractions, Microsoft.Extensions.Diagnostics, Microsoft.Extensions.Options.ConfigurationExtensions and Polly packages instead. [1][2]

Sources:

• Microsoft.Extensions.Http.Resilience 10.2.0 (NuGet). [1]
• Package dependency summary (mirror). [2]

---

🌐 Web query:

Microsoft.Extensions.Http 10.0.2 dependencies Configuration.Abstractions DependencyInjection.Abstractions

💡 Result:

Yes — Microsoft.Extensions.Http v10.0.2 depends on:

• Microsoft.Extensions.Configuration.Abstractions (>= 10.0.2). [1]
• Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.2). [1]

Source: NuGet package metadata for Microsoft.Extensions.Http 10.0.2. [1]

References
[1] NuGet — Microsoft.Extensions.Http 10.0.2 (package details & dependencies).

---

🌐 Web query:

Microsoft.Extensions.Options 10.0.1 version available NuGet

💡 Result:

Yes — Microsoft.Extensions.Options version 10.0.1 is available on NuGet (published 12/09/2025). Install with:
dotnet add package Microsoft.Extensions.Options --version 10.0.1. [1]

Sources
[1] NuGet package: Microsoft.Extensions.Options 10.0.1.

---

🌐 Web query:

NU1605 downgrade warning .NET NuGet

💡 Result:

NU1605 = "Detected package downgrade" (NuGet restore warning). It means restore picked a lower version of a package than some dependency requested (direct-dependency-wins / version conflict). Common causes:

• A direct reference in your project specifies an older version than a transitive dependency requires.
• A package author explicitly downgraded a transitive dependency.
• Old .NET Core package combinations + RuntimeIdentifier (System.* / Microsoft.* 4.0.0–4.3.1) producing runtime. conflicts.

How to fix (pick the simplest appropriate option):

• Add/upgrade a direct PackageReference to the higher (requested) version in the project that shows the warning. Example:
  dotnet add package PackageB --version 4.0.0
  or edit the in the .csproj. (learn.microsoft.com)
• For .NET Core 3+ projects with the System.* runtime/RID downgrade, add Microsoft.NETCore.Targets (match SDK major) as a PrivateAssets package. (learn.microsoft.com)
• Update the .NET SDK if the warning involves Microsoft.NETCore.App auto-references (older SDKs auto-reference older versions). (learn.microsoft.com)
• If you intentionally accept the downgrade, you can suppress the warning (or avoid TreatWarningsAsErrors for NU1605), but that risks runtime issues. (learn.microsoft.com)

If you want, paste the NU1605 diagnostic text (or your project.assets.json / project file) and I’ll show the exact package(s) to add or change.

Citations:

• 1: https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1605?utm_source=openai
• 2: https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1605?utm_source=openai
• 3: https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1605?utm_source=openai
• 4: https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1605?utm_source=openai

---

🌐 Web query:

Microsoft.Extensions.Configuration.Abstractions 10.0.2 NuGet available

💡 Result:

Yes — Microsoft.Extensions.Configuration.Abstractions version 10.0.2 is available on NuGet (published 2026-01-13). Install examples:

• dotnet: dotnet add package Microsoft.Extensions.Configuration.Abstractions --version 10.0.2
• PackageReference: . [1][2]

Sources:
[1] NuGet package page for Microsoft.Extensions.Configuration.Abstractions.
[2] NuGet version listing for Microsoft.Extensions.Configuration.Abstractions (10.0.2 entry).

---

🌐 Web query:

Microsoft.Extensions.DependencyInjection.Abstractions 10.0.2 NuGet available

💡 Result:

Yes — Microsoft.Extensions.DependencyInjection.Abstractions version 10.0.2 is published on NuGet (last updated January 13, 2026). Install with:

dotnet add package Microsoft.Extensions.DependencyInjection.Abstractions --version 10.0.2

[1] [2]

---

Resolve NU1605 downgrades by pinning Microsoft.Extensions. packages to align with 10.x dependency graph.*

The project has a conflict: Refit.HttpClientFactory 9.0.2 requires Microsoft.Extensions.Http >= 9.0.3, which downgrades the transitive requirement from Microsoft.Extensions.Http 10.0.2. This triggers NU1605 warnings for Microsoft.Extensions.Configuration.Abstractions, Microsoft.Extensions.DependencyInjection.Abstractions, and Microsoft.Extensions.Options.

Add explicit references to pin these to versions matching the 10.0.2 requirement:

🔧 Suggested fix (project-local pin)

 <ItemGroup>
   <PackageReference Include="Microsoft.Extensions.Http.Resilience" Version="10.2.0" />
   <PackageReference Include="Refit.HttpClientFactory" Version="9.0.2" />
   <PackageReference Include="Microsoft.Extensions.Http.Polly" Version="10.0.2" />
+  <PackageReference Include="Microsoft.Extensions.Configuration.Abstractions" Version="10.0.2" />
+  <PackageReference Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="10.0.2" />
+  <PackageReference Include="Microsoft.Extensions.Options" Version="10.0.2" />
   <PackageReference Include="Polly.Contrib.WaitAndRetry" Version="1.1.1" />
 </ItemGroup>

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	<ItemGroup>
	<PackageReference Include="Microsoft.Extensions.Http.Resilience" Version="10.1.0" />
	<PackageReference Include="Microsoft.Extensions.Http.Resilience" Version="10.2.0" />
	<PackageReference Include="Refit.HttpClientFactory" Version="9.0.2" />
	<PackageReference Include="Microsoft.Extensions.Http.Polly" Version="10.0.1" />
	<PackageReference Include="Microsoft.Extensions.Http.Polly" Version="10.0.2" />
	<PackageReference Include="Polly.Contrib.WaitAndRetry" Version="1.1.1" />
	<ItemGroup>
	<PackageReference Include="Microsoft.Extensions.Http.Resilience" Version="10.2.0" />
	<PackageReference Include="Refit.HttpClientFactory" Version="9.0.2" />
	<PackageReference Include="Microsoft.Extensions.Http.Polly" Version="10.0.2" />
	<PackageReference Include="Microsoft.Extensions.Configuration.Abstractions" Version="10.0.2" />
	<PackageReference Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="10.0.2" />
	<PackageReference Include="Microsoft.Extensions.Options" Version="10.0.2" />
	<PackageReference Include="Polly.Contrib.WaitAndRetry" Version="1.1.1" />

🤖 Prompt for AI Agents

In `@test/MSBuild/Refitter.MSBuild.Tests.csproj` around lines 11 - 15, Pin the
conflicting Microsoft.Extensions.* packages by adding explicit PackageReference
entries for Microsoft.Extensions.Configuration.Abstractions,
Microsoft.Extensions.DependencyInjection.Abstractions, and
Microsoft.Extensions.Options set to version 10.0.2 (to match the
Microsoft.Extensions.Http 10.x graph) so the project-local references override
the transitive downgrade from Refit.HttpClientFactory 9.0.2; update the project
file to include these three package references
(Microsoft.Extensions.Configuration.Abstractions,
Microsoft.Extensions.DependencyInjection.Abstractions,
Microsoft.Extensions.Options) at version 10.0.2.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud