← Explore all agents

MIGRATION / GitHub community

.NET solution upgrade planner

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

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

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.

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 ↗
  1. Read the pinned source and its licence, then configure an explicitly bounded host context.
  2. 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.
  3. 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

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/dotnet-upgrade.agent.md

    Supports: Workflow, inputs, outputs and stated boundaries

  2. Applicable licence ↗Checked

    https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE

    Supports: Redistribution and attribution

  3. https://docs.github.com/en/copilot/reference/custom-agents-configuration

    Supports: Host loading and effective permission boundaries

  4. https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet

    Supports: Dependency setup and source-review boundary

Evidence & Ask