Add Instructions , Prompts, Chatmode options to Upgrade a dotnet solution to higher version #322
+627
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
aaronpowell
requested changes
Oct 16, 2025
There was a problem hiding this comment.
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.
|
Please run the update script so the appropriate readmes are updated. |
Yes Addressed |
aaronpowell
approved these changes
Oct 21, 2025
There was a problem hiding this comment.
Do you think these could be useful in the C#/.NET collection - https://github.com/github/awesome-copilot/blob/main/collections/csharp-dotnet-development.md?
If so, feel free to send that as a PR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
node update-readme.jsand verified thatREADME.mdis 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
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.