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

[christianhelle]

Summary by CodeRabbit

• New Features
  • Automatic runtime selection: prefers .NET 9 when available, otherwise uses .NET 8.
  • Clearer logs indicating the chosen runtime and executed command.
• Chores
  • Updated package layout: ships MSBuild task assets for both .NET 8 and .NET 9 with versioned paths.
• Tests
  • Added an end-to-end build script to validate packaging and MSBuild integration.

[coderabbitai]

Walkthrough

Updates MSBuild packaging paths to versioned task folders, adds .NET runtime detection in RefitterGenerateTask to choose net8.0 or net9.0 refitter.dll at runtime, and introduces a Bash script to perform an end-to-end local build, pack, and test cycle for the MSBuild integration.

Changes

Cohort / File(s)	Summary
MSBuild packaging paths src/Refitter.MSBuild/Refitter.MSBuild.csproj	Adjusts Content PackagePath for net8.0 to "tasks/net8.0" and adds net9.0 Content at "tasks/net9.0"; includes respective build outputs.
Runtime selection in task src/Refitter.MSBuild/RefitterGenerateTask.cs	Adds runtime detection via parsing dotnet --list-runtimes. Defaults to net8.0 but switches to net9.0 if a 9.x runtime is present. Refactors argument construction and logging; removes pre-check for refitter.dll existence.
E2E test/build script test/MSBuild/build.sh	New Bash script to clean, restore, build, pack MSBuild package, add local nupkg source, restore and run with verbose logs, then clean up.

Sequence Diagram(s)

sequenceDiagram
    participant MSB as MSBuild
    participant Task as RefitterGenerateTask
    participant CLI as dotnet CLI
    participant RT as Installed Runtimes
    participant DLL as refitter.dll (net8.0 or net9.0)

    MSB->>Task: Execute()
    Task->>CLI: dotnet --list-runtimes
    CLI-->>Task: list of runtimes
    Task->>RT: Inspect for Microsoft.NETCore.App 9.x
    alt .NET 9 found
        Task->>Task: Select path .../net9.0/refitter.dll
        Task-->>MSB: Log "Using .NET 9"
    else .NET 9 not found
        Task->>Task: Select path .../net8.0/refitter.dll
        Task-->>MSB: Log "Using .NET 8"
    end
    Task->>CLI: dotnet [args] <path to DLL> [...options]
    CLI->>DLL: Launch generator
    DLL-->>Task: Generate files
    Task-->>MSB: Return existing generated files

Loading

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 — Also modifies RefitterGenerateTask to change how outputs are produced and parsed; closely related to task execution flow.

Pre-merge checks (2 passed, 1 warning)

❌ 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%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title accurately and concisely summarizes the primary change — adding support for systems with only .NET 9.0 in Refitter.MSBuild via runtime detection and packaging — and is directly relevant to the changes in the changeset.

Poem

A hop, a skip, I sniff the runtime breeze,
net8.0 burrows, net9.0 in the trees.
I pack my tasks in versioned nests,
then build and run my fluffy tests.
With dotnet tracks and pawprint logs,
I ship my bits—swift rabbit jogs. 🐇✨

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch msbuild

---

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 systems running only .NET 9.0 (without .NET 8.0) in Refitter.MSBuild by implementing runtime detection and dynamic path resolution. The changes ensure the MSBuild task can use the appropriate .NET version of the CLI tool based on what's installed on the system.

• Adds runtime detection logic to identify available .NET versions
• Updates package structure to include both .NET 8.0 and 9.0 versions
• Implements fallback logic prioritizing .NET 9.0 when available

Reviewed Changes

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

File	Description
src/Refitter.MSBuild/RefitterGenerateTask.cs	Adds runtime detection and dynamic path resolution for .NET 8/9 CLI executables
src/Refitter.MSBuild/Refitter.MSBuild.csproj	Updates package structure to include both .NET 8.0 and 9.0 binaries in separate folders
test/MSBuild/build.sh	Adds test script for MSBuild integration testing

[Copilot]

The code no longer validates if the refitterDll file exists before attempting to execute it. The original file existence check was removed but not replaced, which could lead to runtime errors when the selected .NET version's DLL is missing.

[Copilot]

The method doesn't handle process execution failures or capture stderr output. If the 'dotnet' command fails or isn't found, the method will silently return an empty list, causing the runtime detection to fail without proper error reporting.

Suggested change

	private static List<string> GetInstalledDotnetRuntimes()
	{
	var installedRuntimes = new List<string>();
	using (var process = new Process())
	{
	process.StartInfo.FileName = "dotnet";
	process.StartInfo.Arguments = "--list-runtimes";
	process.StartInfo.RedirectStandardOutput = true;
	process.StartInfo.UseShellExecute = false;
	process.StartInfo.CreateNoWindow = true;
	process.Start();
	using (var reader = process.StandardOutput)
	{
	var output = reader.ReadToEnd();
	installedRuntimes.AddRange(output?.Split([Environment.NewLine], StringSplitOptions.RemoveEmptyEntries));
	}
	process.WaitForExit();
	}
	private List<string> GetInstalledDotnetRuntimes()
	{
	var installedRuntimes = new List<string>();
	try
	{
	using (var process = new Process())
	{
	process.StartInfo.FileName = "dotnet";
	process.StartInfo.Arguments = "--list-runtimes";
	process.StartInfo.RedirectStandardOutput = true;
	process.StartInfo.RedirectStandardError = true;
	process.StartInfo.UseShellExecute = false;
	process.StartInfo.CreateNoWindow = true;
	process.Start();
	string output = process.StandardOutput.ReadToEnd();
	string error = process.StandardError.ReadToEnd();
	process.WaitForExit();
	if (process.ExitCode != 0)
	{
	TryLogError($"Failed to execute 'dotnet --list-runtimes'. Exit code: {process.ExitCode}. Error: {error}");
	return new List<string>();
	}
	if (!string.IsNullOrWhiteSpace(error))
	{
	TryLogError($"Error output from 'dotnet --list-runtimes': {error}");
	}
	installedRuntimes.AddRange(output?.Split([Environment.NewLine], StringSplitOptions.RemoveEmptyEntries));
	}
	}
	catch (Exception ex)
	{
	TryLogError($"Exception while executing 'dotnet --list-runtimes': {ex.Message}");
	return new List<string>();
	}

[Copilot]

The null-conditional operator on output is unnecessary since Split is called on a potentially null string. If output is null, this will throw a NullReferenceException. Should use output?.Split(...) ?? [] or check for null explicitly before splitting.

Suggested change

	installedRuntimes.AddRange(output?.Split([Environment.NewLine], StringSplitOptions.RemoveEmptyEntries));
	installedRuntimes.AddRange(output?.Split([Environment.NewLine], StringSplitOptions.RemoveEmptyEntries) ?? Array.Empty<string>());

[sonarqubecloud]

Quality Gate failed

Failed conditions
1 Security Hotspot

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.52%. Comparing base (b791fa9) to head (2d68dd3).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #746      +/-   ##
==========================================
+ Coverage   95.47%   98.52%   +3.05%     
==========================================
  Files          60       60              
  Lines        2982     2918      -64     
==========================================
+ Hits         2847     2875      +28     
+ Misses        102        4      -98     
- Partials       33       39       +6     

Flag	Coverage Δ
unittests	98.52% <ø> (+3.05%)	⬆️

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: 5

🧹 Nitpick comments (2)

test/MSBuild/build.sh (1)

20-20: Consider capturing build output for debugging.

The verbose logging with -filelogger will create an msbuild.log file, but it's not mentioned or cleaned up.

Apply this diff to handle the log file:

 dotnet run -v d -filelogger
+
+# Display log file location for debugging
+if [ -f msbuild.log ]; then
+    echo "Build log saved to: $(pwd)/msbuild.log"
+fi
+
 dotnet remove package Refitter.MSBuild
 rm -f Refitter.MSBuild.*.nupkg
+rm -f msbuild.log  # Clean up log file

src/Refitter.MSBuild/RefitterGenerateTask.cs (1)

67-67: Typo in variable name: "seperator" should be "separator".

The variable name has a spelling error that appears multiple times in the code.

Apply this diff to fix the typo:

-        var seperator = Path.DirectorySeparatorChar;
-        var refitterDll = $"{packageFolder}{seperator}..{seperator}net8.0{seperator}refitter.dll";
+        var separator = Path.DirectorySeparatorChar;
+        var refitterDll = $"{packageFolder}{separator}..{separator}net8.0{separator}refitter.dll";

And update line 73 as well:

-            refitterDll = $"{packageFolder}{seperator}..{seperator}net9.0{seperator}refitter.dll";
+            refitterDll = $"{packageFolder}{separator}..{separator}net9.0{separator}refitter.dll";

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d231d5e and 2d68dd3.

📒 Files selected for processing (3)

• src/Refitter.MSBuild/Refitter.MSBuild.csproj (1 hunks)
• src/Refitter.MSBuild/RefitterGenerateTask.cs (2 hunks)
• test/MSBuild/build.sh (1 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

**/*.cs

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

**/*.cs: Follow existing C# coding conventions defined in .editorconfig
Use PascalCase for public members and camelCase for parameters and local variables
Use meaningful variable and method names
Keep methods focused with single responsibility

Files:

• src/Refitter.MSBuild/RefitterGenerateTask.cs

src/{Refitter,Refitter.Core,Refitter.SourceGenerator,Refitter.MSBuild}/**/*.cs

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Include XML documentation for public APIs

Files:

• src/Refitter.MSBuild/RefitterGenerateTask.cs

🧠 Learnings (3)

📓 Common learnings

Learnt from: CR
PR: christianhelle/refitter#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-08-13T18:27:12.292Z
Learning: Before committing, run 'dotnet format src/Refitter.sln' and ensure 'dotnet format --verify-no-changes' passes

Learnt from: CR
PR: christianhelle/refitter#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-08-13T18:27:12.292Z
Learning: Install .NET 8.0 and 9.0 SDKs and ensure PATH is set as described before building or testing

📚 Learning: 2025-08-13T18:27:12.292Z

Learnt from: CR
PR: christianhelle/refitter#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-08-13T18:27:12.292Z
Learning: Applies to src/{Refitter,Refitter.Core,Refitter.SourceGenerator,Refitter.MSBuild}/**/*.cs : Include XML documentation for public APIs

Applied to files:

• src/Refitter.MSBuild/Refitter.MSBuild.csproj

📚 Learning: 2025-08-13T18:27:12.292Z

Learnt from: CR
PR: christianhelle/refitter#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-08-13T18:27:12.292Z
Learning: Before committing, run 'dotnet format src/Refitter.sln' and ensure 'dotnet format --verify-no-changes' passes

Applied to files:

• src/Refitter.MSBuild/Refitter.MSBuild.csproj
• test/MSBuild/build.sh

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: 👌 Verify build
• GitHub Check: 👌 Verify build
• GitHub Check: script
• GitHub Check: 👌 Verify build
• GitHub Check: Analyze (csharp)

🔇 Additional comments (2)

src/Refitter.MSBuild/Refitter.MSBuild.csproj (1)

27-28: LGTM! The multi-runtime packaging structure aligns well with the runtime detection logic.

The separation of net8.0 and net9.0 content into versioned task folders enables the MSBuild task to select the appropriate runtime at execution time.

src/Refitter.MSBuild/RefitterGenerateTask.cs (1)

115-136: Add XML documentation for the new public method.

According to the coding guidelines, public APIs in this project should include XML documentation.

Apply this diff to add XML documentation:

+    /// <summary>
+    /// Gets the list of installed .NET runtimes by invoking 'dotnet --list-runtimes'.
+    /// </summary>
+    /// <returns>A list of installed runtime descriptions.</returns>
     private static List<string> GetInstalledDotnetRuntimes()

Actually, since this is a private method, XML documentation is not required. The method visibility is appropriate.

[coderabbitai]

🛠️ Refactor suggestion

Add fallback for when the dotnet command fails to detect runtimes.

The runtime detection could fail if the dotnet command is not available or returns an error. Consider adding error handling.

Apply this diff to add error handling:

         var refitterDll = $"{packageFolder}{seperator}..{seperator}net8.0{seperator}refitter.dll";
 
-        List<string> installedRuntimes = GetInstalledDotnetRuntimes();
-        if (installedRuntimes.Any(r => r.StartsWith("Microsoft.NETCore.App 9.")))
+        try
         {
-            // Use .NET 9 version if available
-            refitterDll = $"{packageFolder}{seperator}..{seperator}net9.0{seperator}refitter.dll";
-            TryLogCommandLine("Detected .NET 9 runtime. Using .NET 9 version of Refitter.");
+            List<string> installedRuntimes = GetInstalledDotnetRuntimes();
+            if (installedRuntimes.Any(r => r.StartsWith("Microsoft.NETCore.App 9.")))
+            {
+                // Use .NET 9 version if available
+                refitterDll = $"{packageFolder}{seperator}..{seperator}net9.0{seperator}refitter.dll";
+                TryLogCommandLine("Detected .NET 9 runtime. Using .NET 9 version of Refitter.");
+            }
+            else
+            {
+                TryLogCommandLine("Using .NET 8 version of Refitter.");
+            }
         }
-        else
+        catch (Exception ex)
         {
-            TryLogCommandLine("Using .NET 8 version of Refitter.");
+            TryLogCommandLine($"Failed to detect .NET runtimes: {ex.Message}. Defaulting to .NET 8 version.");
         }

📝 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

	var expectedFiles = GetExpectedGeneratedFiles(file);
	var assembly = Assembly.GetExecutingAssembly();
	var packageFolder = Path.GetDirectoryName(assembly.Location);
	var seperator = Path.DirectorySeparatorChar;
	var refitterDll = $"{packageFolder}{seperator}..{seperator}refitter.dll";
	var refitterDll = $"{packageFolder}{seperator}..{seperator}net8.0{seperator}refitter.dll";
	var args = $"{refitterDll} --settings-file {file}";
	if (DisableLogging)
	List<string> installedRuntimes = GetInstalledDotnetRuntimes();
	if (installedRuntimes.Any(r => r.StartsWith("Microsoft.NETCore.App 9.")))
	{
	args += " --no-logging";
	// Use .NET 9 version if available
	refitterDll = $"{packageFolder}{seperator}..{seperator}net9.0{seperator}refitter.dll";
	TryLogCommandLine("Detected .NET 9 runtime. Using .NET 9 version of Refitter.");
	}
	else
	{
	TryLogCommandLine("Using .NET 8 version of Refitter.");
	}
	var expectedFiles = GetExpectedGeneratedFiles(file);
	var assembly = Assembly.GetExecutingAssembly();
	var packageFolder = Path.GetDirectoryName(assembly.Location);
	var seperator = Path.DirectorySeparatorChar;
	var refitterDll = $"{packageFolder}{seperator}..{seperator}net8.0{seperator}refitter.dll";
	try
	{
	List<string> installedRuntimes = GetInstalledDotnetRuntimes();
	if (installedRuntimes.Any(r => r.StartsWith("Microsoft.NETCore.App 9.")))
	{
	// Use .NET 9 version if available
	refitterDll = $"{packageFolder}{seperator}..{seperator}net9.0{seperator}refitter.dll";
	TryLogCommandLine("Detected .NET 9 runtime. Using .NET 9 version of Refitter.");
	}
	else
	{
	TryLogCommandLine("Using .NET 8 version of Refitter.");
	}
	}
	catch (Exception ex)
	{
	TryLogCommandLine($"Failed to detect .NET runtimes: {ex.Message}. Defaulting to .NET 8 version.");
	}

🤖 Prompt for AI Agents

In src/Refitter.MSBuild/RefitterGenerateTask.cs around lines 63 to 79, the code
assumes GetInstalledDotnetRuntimes() always succeeds and will throw or return
nothing if the dotnet command is missing; wrap the call in a try/catch (or
otherwise detect failures) so exceptions are caught and logged via
TryLogCommandLine/TryLogError, treat failures as “unknown” and fall back to
using the .NET 8 refitter.dll path, and ensure you also handle an empty list
case by falling back to .NET 8 and logging a warning that runtime detection
failed so the build continues with the safe default.

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

Verify that the refitter.dll exists before attempting to execute.

The previous version had a check to ensure the refitter.dll file exists. Without this check, the error message might be less clear if the file is missing.

Let me verify if there's any validation elsewhere in the codebase:

---

🏁 Script executed:

#!/bin/bash
# Check if there's any file existence validation for refitter.dll
rg -n "File\.Exists.*refitter" --type cs
rg -n "refitter\.dll" --type cs -C3

Length of output: 1327

---

Add a File.Exists guard for refitter.dll before executing.

No existence check was found in src/Refitter.MSBuild/RefitterGenerateTask.cs — refitterDll is built around line ~67 and args are assembled at lines 81–85; add a guard like if (!File.Exists(refitterDll)) { Log.LogError($"Refitter not found at '{refitterDll}'"); return false; } so failures are clear.

🤖 Prompt for AI Agents

In src/Refitter.MSBuild/RefitterGenerateTask.cs around lines 81–85 (refitterDll
is constructed near line ~67), add a File.Exists check for refitterDll before
assembling or executing the args; if the file does not exist call Log.LogError
with a clear message including the refitterDll path and return false to abort
the task so failures are explicit and surfaced.

[coderabbitai]

⚠️ Potential issue

Potential NullReferenceException when splitting output.

The null-conditional operator ?. is used with Split, but the result is then passed to AddRange which doesn't handle null gracefully.

Apply this diff to handle potential null output:

-                installedRuntimes.AddRange(output?.Split([Environment.NewLine], StringSplitOptions.RemoveEmptyEntries));
+                if (!string.IsNullOrEmpty(output))
+                {
+                    installedRuntimes.AddRange(output.Split([Environment.NewLine], StringSplitOptions.RemoveEmptyEntries));
+                }

📝 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

	installedRuntimes.AddRange(output?.Split([Environment.NewLine], StringSplitOptions.RemoveEmptyEntries));
	if (!string.IsNullOrEmpty(output))
	{
	installedRuntimes.AddRange(output.Split(new[] { Environment.NewLine }, StringSplitOptions.RemoveEmptyEntries));
	}

🤖 Prompt for AI Agents

In src/Refitter.MSBuild/RefitterGenerateTask.cs around line 130, the code calls
AddRange(output?.Split([Environment.NewLine],
StringSplitOptions.RemoveEmptyEntries)) which can pass null to AddRange if
output is null; change it so AddRange receives a non-null sequence (for example
use the null-coalescing operator to supply Array.Empty<string>() or an empty
enumerable when output is null) so AddRange is never called with a null
argument.

[coderabbitai]

🛠️ Refactor suggestion

Add error handling and make the script more robust.

The script lacks error handling which could lead to silent failures or incomplete cleanup. Consider adding set -e to exit on errors and trap cleanup operations.

Apply this diff to add error handling:

 #!/bin/bash
+set -e  # Exit on error
+
+# Trap to ensure cleanup even on failure
+trap 'echo "Build failed. Cleaning up..."; rm -f Refitter.MSBuild.*.nupkg' ERR
 
 rm -rf bin
 rm -rf obj

Also consider checking if required tools are available:

# Check required tools
for cmd in dotnet find; do
    if ! command -v $cmd &> /dev/null; then
        echo "Error: $cmd is not installed"
        exit 1
    fi
done

🤖 Prompt for AI Agents

In test/MSBuild/build.sh around lines 1 to 22, the script lacks error handling
and checks for required commands; update it to fail fast and perform guaranteed
cleanup by adding "set -euo pipefail" (or at least "set -e"), add a trap to run
cleanup on EXIT (removing temporary files and shutting down build server), and
explicitly verify required tools (dotnet and find) are available before
proceeding, printing a clear error and exiting if missing; also ensure each
critical command is allowed to fail the script (no silent ignores) and log
failures with descriptive messages so failures are visible.

[coderabbitai]

⚠️ Potential issue

The find command may fail if no .nupkg files exist.

The find command with -exec will fail if no matching files are found, which could happen on first run or after cleanup.

Apply this diff to handle the case when no packages are found:

 # Find the nupkg file and add it as a package
-find . -name "Refitter.MSBuild.*.nupkg" -exec dotnet add package {} --source . \;
+NUPKG_FILES=$(find . -name "Refitter.MSBuild.*.nupkg" 2>/dev/null || true)
+if [ -n "$NUPKG_FILES" ]; then
+    echo "$NUPKG_FILES" | xargs -I {} dotnet add package {} --source .
+else
+    echo "Error: No .nupkg files found after packing"
+    exit 1
+fi

📝 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

	find . -name "Refitter.MSBuild.*.nupkg" -exec dotnet add package {} --source . \;
	# Find the nupkg file and add it as a package
	NUPKG_FILES=$(find . -name "Refitter.MSBuild.*.nupkg" 2>/dev/null || true)
	if [ -n "$NUPKG_FILES" ]; then
	echo "$NUPKG_FILES" | xargs -I {} dotnet add package {} --source .
	else
	echo "Error: No .nupkg files found after packing"
	exit 1
	fi

🤖 Prompt for AI Agents

In test/MSBuild/build.sh around line 16 the find command uses -exec which causes
the script to exit/fail when no Refitter.MSBuild.*.nupkg files exist; replace
that single-line command with a safe variant that does nothing when there are no
matches (for example use find ... -print0 piped to xargs -0 with the GNU xargs
-r/--no-run-if-empty option, or use find -exec sh -c 'dotnet add package "$1"
--source .' _ {} \; wrapped to ignore missing results) so the script continues
without error when no .nupkg files are found.