Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

kshashank57
Copy link

@kshashank57 kshashank57 commented Oct 16, 2025

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • My contribution adds a new instruction, prompt, or chat mode file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, or chat mode with GitHub Copilot.
  • I have run node update-readme.js and verified that README.md is up to date.

Description

This PR introduces a standardized, chatmode-compatible guidance file for performing .NET upgrades across multi-project solutions.
The document provides a generic and adaptive playbook that automatically adjusts based on the repository’s current .NET version and outlines discovery, planning, execution, and validation workflows.

Key Highlights

Added dotnet-upgrade.chatmode.md for automated upgrade guidance

Supports detecting current .NET versions from the solution using shell and dotnet commands

Provides structured chat prompts to generate:

Upgrade sequences

Dependency-aware upgrade order

Per-project upgrade instructions and validation steps

Includes CI/CD update templates for Azure DevOps and GitHub Actions

Designed to remain version-agnostic — supports upgrades from any .NET version to the next stable LTS

Intended Usage

This file acts as a playbook for engineering teams or Copilot agents to:

Discover framework versions dynamically

Recommend upgrade paths (e.g., net6.0 → net8.0 → net9.0)

Automate validation, testing, and PR generation steps

Validation

Verified file renders correctly in markdown preview

Confirmed content is generic, reusable, and consistent with best practices

Checked auto-detection and upgrade command examples for accuracy


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New chat mode file.
  • Other (please specify):

Additional Notes


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

Added comprehensive instructions for upgrading .NET projects, including preparation steps, upgrade strategies, and handling breaking changes.
This document provides a comprehensive set of prompts for analyzing, planning, executing, and validating framework upgrades for multi-project .NET solutions, covering various aspects from project discovery to final validation.
Added a comprehensive playbook for upgrading .NET projects, including guidance on discovery, analysis, upgrade sequences, and CI/CD configuration.
Copy link
Contributor

@aaronpowell aaronpowell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please review the Contributing guide as these files don't meet the naming requirements, are lacking front matter and the readmes aren't updated.

Updated .NET upgrade chatmode guidance with detailed instructions and tools for project migration and modernization.
Updated the instructions for .NET Framework upgrades to include a name and description for the specialized agent, and refined the prompt example for clarity.
Updated prompts for .NET upgrade analysis, enhancing project classification, dependency review, and upgrade strategy sections. Added new prompts for CI/CD updates, testing, and documentation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.