---
title: ".NET solution upgrade planner: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/github-dotnet-upgrade/
description: "A solution-upgrade reference organizing framework discovery, dependency order and validation checkpoints."
---

# .NET solution upgrade planner: review, role & definition · Undominated.ai

> A solution-upgrade reference organizing framework discovery, dependency order and validation checkpoints.

[← Explore all agents](/agents/)

MIGRATION / GitHub community

# .NET solution upgrade planner

A solution-upgrade reference organizing framework discovery, dependency order and validation checkpoints.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/dotnet-upgrade.agent.md)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 4 linked sources
 Publisher GitHub community
 Licence [MIT ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE)
 Revision f25421d3f1b8
 [Read what was—and wasn’t—checked ↓](#review)

“Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.”

 [GitHub community · upstream description ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/dotnet-upgrade.agent.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - It sequences independent libraries before shared components and application projects to expose compatibility issues incrementally.
- Discovery includes installed SDKs, target frameworks, outdated packages and a restore graph rather than changing one version string blindly.

### A good fit for

 - Supply solution projects, framework targets, package constraints and the supported deployment environments.
- Produce an upgrade inventory and phased plan followed by separately authorized edits and validation.

### Weigh up before choosing

 - The embedded shell examples and netstandard migration rule are not universally appropriate; current support windows, consumer compatibility and multi-targeted projects require a real assessment.
- Source-only component: inspect its upstream context and dependencies before adapting it; no standalone runnable bundle is offered.
- The Automation section incorrectly says dotnet --list-sdks discovers new releases; it lists SDKs already installed. Use an actual Microsoft release source for upgrade detection.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - agents/dotnet-upgrade.agent.md (pinned complete source retained)
- LICENSE
- Repository README and current official host configuration documentation

### Our findings

 - It sequences independent libraries before shared components and application projects to expose compatibility issues incrementally.
- Discovery includes installed SDKs, target frameworks, outdated packages and a restore graph rather than changing one version string blindly.

### Not established by this review

 - Source review only: no agent was installed or invoked. Task correctness, effective host restrictions and integration behaviour were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Use the role in your project.

[Upstream setup instructions ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/dotnet-upgrade.agent.md)
 - Read the pinned source and its licence, then configure an explicitly bounded host context.
- Verify Microsoft’s current target support and the solution’s consumers, provide the requested documentation connector, and run build/runtime tests for each deployment target.
- Supply solution projects, framework targets, package constraints and the supported deployment environments.

### Before you start

 - Compatible .NET SDK/build environment
- Project dependency and consumer constraints
- Microsoft documentation access or MCP connector

### Compatibility

GitHub Copilot

### Implementation

Markdown

### Host-mediated agent profile

 - Declared tools: codebase, edit/editFiles, search, runCommands, runTasks, runTests, problems, changes, usages, findTestFiles, testFailure, terminalLastCommand, terminalSelection, web/fetch, microsoft.docs.mcp. Effective host permissions still govern access; shell or execution tools can write files and contact networks.

### Cost model

The definition has the stated open-source licence. Model/host usage and any connected service or execution environment can incur separate costs.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned upstream agent definition ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/dotnet-upgrade.agent.md) Checked 2026-10-14 https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/dotnet-upgrade.agent.md Supports: Workflow, inputs, outputs and stated boundaries
- [Applicable licence ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE) Checked 2026-10-14 https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE Supports: Redistribution and attribution
- [Host configuration and tool inheritance ↗](https://docs.github.com/en/copilot/reference/custom-agents-configuration) Checked 2026-10-14 https://docs.github.com/en/copilot/reference/custom-agents-configuration Supports: Host loading and effective permission boundaries
- [Microsoft dotnet installed-SDK command semantics ↗](https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet) Checked 2026-10-14 https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet Supports: Dependency setup and source-review boundary

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Arm workload migration assistant ↗ An Arm migration workflow that checks source, dependency and container architecture assumptions through the Arm MCP service.](/agents/github-arm-migration/)[### C# Reviewer ↗ Reviews C# changes by running dotnet build and dotnet format verification before reading the diff, then ranks findings from SQL injection and async misuse to nullable reference types and EF Core traps.](/agents/ecc-csharp-reviewer/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
