jongalloway / jongalloway/dotnet-mcp

Add .NET Migration Assistant Tools

Open
#53 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: migration needs-discussion priority: low size: XL
Dominant language
C#
Stars
36
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Description

Help users migrate from .NET Framework to modern .NET with automated analysis and guidance.

Motivation

Many teams still need to migrate:

  • .NET Framework → .NET 9+
  • Older .NET versions → Latest
  • Detect breaking changes
  • API compatibility checking

Proposed Tools

New MCP Tools
  • dotnet_migration_analyze

    • Analyze .NET Framework projects
    • Identify blocking issues
    • Estimate effort
  • dotnet_migration_suggest

    • Suggest migration path
    • Breaking changes list
    • Modern alternatives for deprecated APIs
  • dotnet_migration_validate

    • Check API compatibility
    • Framework feature availability
    • Third-party package compatibility

Implementation Notes

  • Use .NET Upgrade Assistant APIs
  • Analyze code with Roslyn
  • Check API compatibility
  • Provide actionable guidance

Success Criteria

  • Migration analysis
  • Breaking change detection
  • Alternative suggestions
  • Compatibility checking
  • Tests
  • Documentation

Related

  • Part of: Phase 3 roadmap
  • Experimental feature
  • May leverage existing tools

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the repository's existing MCP tools and .NET SDK integration, then review the proposed .NET Upgrade Assistant APIs, Roslyn analysis, and API compatibility checks. Done means the listed migration analysis, suggestions, validation, tests, and documentation are implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.