From 0578daf8d6d8eeb429a426113c93be76767c2be0 Mon Sep 17 00:00:00 2001 From: kshashank57 <57212456+kshashank57@users.noreply.github.com> Date: Thu, 16 Oct 2025 13:27:35 +0530 Subject: [PATCH 1/7] Add .NET project upgrade instructions Added comprehensive instructions for upgrading .NET projects, including preparation steps, upgrade strategies, and handling breaking changes. --- instructions/dotnet-upgrade-instructions.md | 280 ++++++++++++++++++++ 1 file changed, 280 insertions(+) create mode 100644 instructions/dotnet-upgrade-instructions.md diff --git a/instructions/dotnet-upgrade-instructions.md b/instructions/dotnet-upgrade-instructions.md new file mode 100644 index 00000000..1d605472 --- /dev/null +++ b/instructions/dotnet-upgrade-instructions.md @@ -0,0 +1,280 @@ +You are an **specialized agent** for upgrades of .NET Framework please keep going until the desired frameworks upgrade are completely resolved, tested using the instructions below before ending your turn and yielding back to the user. + +Your thinking should be thorough and so it's fine if it's very long. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough. + +You **MUST iterate** and keep going until the problem is solved. + +# .NET Project Upgrade Instructions + +This document provides structured guidance for upgrading a multi-project .NET solution to a higher framework version (e.g., .NET 6 → .NET 8). Upgrade this repository to the latest supported **.NET Core**, **.NET Standard**, or **.NET Framework** version depending on project type, while preserving build integrity, tests, and CI/CD pipelines. +Follow the steps **sequentially** and **do not attempt to upgrade all projects at once**. + +## Preparation +1. **Identify Project Type** + - Inspect each `*.csproj`: + - `netcoreapp*` → **.NET Core / .NET (modern)** + - `netstandard*` → **.NET Standard** + - `net4*` (e.g., net472) → **.NET Framework** + - Note the current target and SDK. + +2. **Select Target Version** + - **.NET (Core/Modern)**: Upgrade to the latest LTS (e.g., `net8.0`). + - **.NET Standard**: Prefer migrating to **.NET 6+** if possible. If staying, target `netstandard2.1`. + - **.NET Framework**: Upgrade to at least **4.8**, or migrate to .NET 6+ if feasible. + +3. **Review Release Notes & Breaking Changes** + - [.NET Core/.NET Upgrade Docs](https://learn.microsoft.com/dotnet/core/whats-new/) + - [.NET Framework 4.x Docs](https://learn.microsoft.com/dotnet/framework/whats-new/) + +--- + +## 1. Upgrade Strategy +1. Upgrade **projects sequentially**, not all at once. +2. Start with **independent class library projects** (least dependencies). +3. Gradually move to projects with **higher dependencies** (e.g., APIs, Azure Functions). +4. Ensure each project builds and passes tests before proceeding to the next. +5. Post Builds are successfull **only after success completion** update the CI/CD files + +--- + +## 2. Determine Upgrade Sequence +To identify dependencies: +- Inspect the solution’s dependency graph. +- Use the following approaches: + - **Visual Studio** → `Dependencies` in Solution Explorer. + - **dotnet CLI** → run: + ```bash + dotnet list .csproj reference + ``` + - **Dependency Graph Generator**: + ```bash + dotnet msbuild .sln /t:GenerateRestoreGraphFile /p:RestoreGraphOutputPath=graph.json + ``` + Inspect `graph.json` to see the dependency order. + +--- + +## 3. Analyze Each Project +For each project: +1. Open the `*.csproj` file. + Example: + ```xml + + + net6.0 + + + + + + + ``` + +2. Check for: + - `TargetFramework` → Change to the desired version (e.g., `net8.0`). + - `PackageReference` → Verify if each NuGet package supports the new framework. + - Run: + ```bash + dotnet list package --outdated + ``` + Update packages: + ```bash + dotnet add package --version + ``` + +3. If `packages.config` is used (legacy), migrate to `PackageReference`: + ```bash + dotnet migrate + ``` + + +4. Upgrade Code Adjustments +After analyzing the nuget packages, review code for any required changes. + +### Examples +- **System.Text.Json vs Newtonsoft.Json** + ```csharp + // Old (Newtonsoft.Json) + var obj = JsonConvert.DeserializeObject(jsonString); + + // New (System.Text.Json) + var obj = JsonSerializer.Deserialize(jsonString); +IHostBuilder vs WebHostBuilder + +csharp +Copy code +// Old +IWebHostBuilder builder = new WebHostBuilder(); + +// New +IHostBuilder builder = Host.CreateDefaultBuilder(args); +Azure SDK Updates + +csharp +Copy code +// Old (Blob storage SDK v11) +CloudBlobClient client = storageAccount.CreateCloudBlobClient(); + +// New (Azure.Storage.Blobs) +BlobServiceClient client = new BlobServiceClient(connectionString); + + +--- + +## 4. Upgrade Process Per Project +1. Update `TargetFramework` in `.csproj`. +2. Update NuGet packages to versions compatible with the target framework. +3. After upgrading and restoring the latest DLLs, review code for any required changes. +4. Rebuild the project: + ```bash + dotnet build .csproj + ``` +5. Run unit tests if any: + ```bash + dotnet test + ``` +6. Fix build or runtime issues before proceeding. + + +--- + +## 5. Handling Breaking Changes +- Review [.NET Upgrade Assistant](https://learn.microsoft.com/dotnet/core/porting/upgrade-assistant) suggestions. +- Common issues: + - Deprecated APIs → Replace with supported alternatives. + - Package incompatibility → Find updated NuGet or migrate to Microsoft-supported library. + - Configuration differences (e.g., `Startup.cs` → `Program.cs` in .NET 6+). + + +--- + +## 6. Validate End-to-End +After all projects are upgraded: +1. Rebuild entire solution. +2. Run all automated tests (unit, integration). +3. Deploy to a lower environment (UAT/Dev) for verification. +4. Validate: + - APIs start without runtime errors. + - Logging and monitoring integrations work. + - Dependencies (databases, queues, caches) connect as expected. + + +--- + +## 7. Tools & Automation +- **.NET Upgrade Assistant**(Optional): + ```bash + dotnet tool install -g upgrade-assistant + upgrade-assistant upgrade .sln``` + +- **Upgrade CI/CD Pipelines**: + When upgrading .NET projects, remember that build pipelines must also reference the correct SDK, NuGet versions, and tasks. + a. Locate pipeline YAML files + - Check common folders such as: + - .azuredevops/ + - .pipelines/ + - Deployment/ + - Root of the repo (*.yml) + +b. Scan for .NET SDK installation tasks + Look for tasks like: + - task: UseDotNet@2 + inputs: + version: + + or + displayName: Use .NET Core sdk + +c. Update SDK version to match the upgraded framework + Replace the old version with the new target version. + Example: + - task: UseDotNet@2 + displayName: Use .NET SDK + inputs: + version: + includePreviewVersions: true # optional, if upgrading to a preview release + +d. Update NuGet Tool version if required + Ensure the NuGet installer task matches the upgraded framework’s needs. + Example: + - task: NuGetToolInstaller@0 + displayName: Use NuGet + inputs: + versionSpec: + checkLatest: true + +e. Validate the pipeline after updates + - Commit changes to a feature branch. + - Trigger a CI build to confirm: + - The YAML is valid. + - The SDK is installed successfully. + - Projects restore, build, and test with the upgraded framework. + +--- + +## 8. Commit Plan +- Always work on the specified branch or branch provided in context, if no branch specified create a new branch (`upgradeNetFramework`). +- Commit after each successful project upgrade. +- If a project fails, rollback to the previous commit and fix incrementally. + + +--- + +## 9. Final Deliverable +- Fully upgraded solution targeting the desired framework version. +- Updated documentation of upgraded dependencies. +- Test results confirming successful build & execution. + +--- + + +## 10. Upgrade Checklist (Per Project) + +Use this table as a sample to track the progress of the upgrade across all projects in the solution and add this in the PullRequest + +| Project Name | Target Framework | Dependencies Updated | Builds Successfully | Tests Passing | Deployment Verified | Notes | +|--------------|------------------|-----------------------|---------------------|---------------|---------------------|-------| +| Project A | ☐ net8.0 | ☐ | ☐ | ☐ | ☐ | | +| Project B | ☐ net8.0 | ☐ | ☐ | ☐ | ☐ | | +| Project C | ☐ net8.0 | ☐ | ☐ | ☐ | ☐ | | + +> ✅ Mark each column as you complete the step for every project. + +## 11. Commit & PR Guidelines + +- Use a **single PR per repository**: + - Title: `Upgrade to .NET [VERSION]` + - Include: + - Updated target frameworks. + - NuGet upgrade summary. + - Provide test results as summarized above. +- Tag with `breaking-change` if APIs were replaced. + +## 12. Multi-Repo Execution (Optional) + +For organizations with multiple repositories: +1. Store this `instructions.md` in a central upgrade template repo. +2. Provide SWE Agent / Cursor with: + ``` + Upgrade all repositories to latest supported .NET versions following instructions.md + ``` +3. Agent should: + - Detect project type per repo. + - Apply the appropriate upgrade path. + - Open PRs for each repo. + + +## 🔑 Notes & Best Practices + +- **Prefer Migration to Modern .NET** + If on .NET Framework or .NET Standard, evaluate moving to .NET 6/8 for long-term support. +- **Automate Tests Early** + CI/CD should block merges if tests fail. +- **Incremental Upgrades** + Large solutions may require upgrading one project at a time. + +### ✅ Example Agent Prompt + +> Upgrade this repository to the latest supported .NET version following the steps in `dotnet-upgrade-instructions.md`. +> Detect project type (.NET Core, Standard, or Framework) and apply the correct migration path. +> Ensure all tests pass and CI/CD workflows are updated. From 8d632d2b3d23f7b67f9f4a574bc6641bd37eb889 Mon Sep 17 00:00:00 2001 From: kshashank57 <57212456+kshashank57@users.noreply.github.com> Date: Thu, 16 Oct 2025 13:34:13 +0530 Subject: [PATCH 2/7] Add .NET Upgrade Prompts documentation 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. --- prompts/dotnet-upgrade-prompts.md | 86 +++++++++++++++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 prompts/dotnet-upgrade-prompts.md diff --git a/prompts/dotnet-upgrade-prompts.md b/prompts/dotnet-upgrade-prompts.md new file mode 100644 index 00000000..6422a75b --- /dev/null +++ b/prompts/dotnet-upgrade-prompts.md @@ -0,0 +1,86 @@ +# .NET Upgrade Prompts + +## Purpose +Prompts for analyzing, planning, executing, and validating framework upgrades for multi-project .NET solutions — including .NET Core, .NET Framework, and .NET Standard migrations. + +## Prompts + +### Project Discovery & Assessment +- Identify all projects in the solution and classify them by type (`.NET Framework`, `.NET Core`, `.NET Standard`). +- Analyze each `.csproj` for its current `TargetFramework` and SDK usage. +- Review external and internal dependencies for framework compatibility. +- Determine the upgrade complexity based on dependency graph depth. +- Identify legacy `packages.config` projects needing migration to `PackageReference`. + +### Upgrade Strategy & Sequencing +- Recommend a project upgrade order from least to most dependent components. +- Suggest how to isolate class library upgrades before API or Azure Function migrations. +- Propose an incremental upgrade strategy with rollback checkpoints. +- Evaluate the use of **Upgrade Assistant** or **manual upgrades** based on project structure. +- Generate an upgrade checklist for tracking build, test, and deployment readiness. + +### Framework Targeting & Code Adjustments +- Suggest the correct `TargetFramework` for each project (e.g., `net8.0`). +- Review and update deprecated SDK or build configurations. +- Identify code patterns needing modernization (e.g., `WebHostBuilder` → `HostBuilder`). +- Suggest replacements for deprecated .NET APIs and third-party libraries. +- Recommend conversion of synchronous calls to async where appropriate. + +### NuGet & Dependency Management +- Analyze outdated or incompatible NuGet packages and suggest compatible versions. +- Identify third-party libraries that lack .NET 8 support and provide migration paths. +- Recommend strategies for handling shared dependency upgrades across projects. +- Evaluate usage of legacy packages and suggest alternatives in Microsoft-supported namespaces. +- Review transitive dependencies and potential version conflicts after upgrade. + +### CI/CD & Build Pipeline Updates +- Analyze YAML build definitions for SDK version pinning and recommend updates. +- Suggest modifications for `UseDotNet@2` and `NuGetToolInstaller` tasks. +- Generate updated build pipeline snippets for .NET 8 migration. +- Recommend validation builds on feature branches before merging to main. +- Identify opportunities to automate test and build verification in CI pipelines. + +### Testing & Validation +- Propose validation checks to ensure the upgraded solution builds and runs successfully. +- Recommend automated test execution for unit and integration suites post-upgrade. +- Generate prompts to verify logging, telemetry, and service connectivity. +- Suggest strategies for verifying backward compatibility and runtime behavior. +- Recommend UAT deployment verification steps before production rollout. + +### Breaking Change Analysis +- Identify deprecated APIs or removed namespaces between target versions. +- Suggest automated scanning using `.NET Upgrade Assistant` and API Analyzer. +- Recommend replacement APIs or libraries for known breaking areas. +- Review configuration changes such as `Startup.cs` → `Program.cs` refactoring. +- Suggest regression testing prompts focused on upgraded API endpoints or services. + +### Version Control & Commit Strategy +- Recommend branching strategy for safe upgrade with rollback capability. +- Generate commit templates for partial and complete project upgrades. +- Suggest best practices for creating structured PRs (`Upgrade to .NET [Version]`). +- Identify tagging strategies for PRs involving breaking changes. +- Recommend peer review focus areas (build, test, and dependency validation). + +### Documentation & Communication +- Suggest how to document each project’s framework change in the PR. +- Propose automated release note generation summarizing upgrades and test results. +- Recommend communicating version upgrades and migration timelines to consumers. +- Generate documentation prompts for dependency updates and validation results. +- Suggest maintaining an upgrade summary dashboard or markdown checklist. + +### Tools & Automation +- Recommend when and how to use: + - `.NET Upgrade Assistant` + - `dotnet list package --outdated` + - `dotnet migrate` + - `graph.json` dependency visualization +- Generate scripts or prompts for analyzing dependency graphs before upgrading. +- Propose AI-assisted prompts for Copilot to identify upgrade issues automatically. +- Suggest how to validate automation output across multiple repositories. + +### Final Validation & Delivery +- Generate prompts to confirm the final upgraded solution passes all validation checks. +- Suggest production deployment verification steps post-upgrade. +- Recommend generating final test results and build artifacts. +- Create a checklist summarizing completion across projects (builds/tests/deployment). +- Generate a release note summarizing framework changes and CI/CD updates. From 99ad64ad61a5eae17abfcdb7ce7787cf22fd86c2 Mon Sep 17 00:00:00 2001 From: kshashank57 <57212456+kshashank57@users.noreply.github.com> Date: Thu, 16 Oct 2025 13:35:24 +0530 Subject: [PATCH 3/7] Create .NET Upgrade Chatmode Guidance document Added a comprehensive playbook for upgrading .NET projects, including guidance on discovery, analysis, upgrade sequences, and CI/CD configuration. --- chatmodes/dotnet_upgrade_chatmode.md | 161 +++++++++++++++++++++++++++ 1 file changed, 161 insertions(+) create mode 100644 chatmodes/dotnet_upgrade_chatmode.md diff --git a/chatmodes/dotnet_upgrade_chatmode.md b/chatmodes/dotnet_upgrade_chatmode.md new file mode 100644 index 00000000..89a7251e --- /dev/null +++ b/chatmodes/dotnet_upgrade_chatmode.md @@ -0,0 +1,161 @@ +# .NET Upgrade — Chatmode Guidance + +> **Purpose:** A generic, ChatGPT-first (chatmode) playbook to discover, plan, execute, and validate .NET upgrades for any multi-project solution. This version automatically adapts to the repository’s current .NET version and provides context-aware upgrade guidance to the next stable version. + +--- + +## Quick Start +1. Run a discovery pass to enumerate all `*.sln` and `*.csproj` files in the repository. +2. Detect the current .NET version(s) used across projects. +3. Identify the latest available stable .NET version (LTS preferred) — usually `+2` years ahead of the existing version. +4. Generate an upgrade plan to move from current → next stable version (e.g., `net6.0 → net8.0`, or `net7.0 → net9.0`). +5. Upgrade one project at a time, validate builds, update tests, and modify CI/CD accordingly. + +--- + +## Auto-Detect Current .NET Version +To automatically detect the current framework versions across the solution: + +```bash +# 1. Check global SDKs installed +dotnet --list-sdks + +# 2. Detect project-level TargetFrameworks +find . -name "*.csproj" -exec grep -H "//;s/<\/TargetFramework>//' | sort | uniq + +# 4. Verify runtime environment +dotnet --info | grep "Version" +``` + +**Chat Prompt:** +> "Analyze the repository and list each project’s current TargetFramework along with the latest available LTS version from Microsoft’s release schedule." + +--- + +## Discovery & Analysis Commands +```bash +# List all projects +dotnet sln list + +# Check current target frameworks for each project +grep -H "TargetFramework" **/*.csproj + +# Check outdated packages +dotnet list .csproj package --outdated + +# Generate dependency graph +dotnet msbuild .csproj /t:GenerateRestoreGraphFile /p:RestoreGraphOutputPath=graph.json +``` + +**Chat Prompt:** +> "Analyze the solution and summarize each project’s current TargetFramework and suggest the appropriate next LTS upgrade version." + +--- + +## Classification Rules +- `TargetFramework` starts with `netcoreapp`, `net5.0+`, `net6.0+`, etc. → **Modern .NET** +- `netstandard*` → **.NET Standard** (migrate to current .NET version) +- `net4*` → **.NET Framework** (migrate via intermediate step to .NET 6+) + +--- + +## Upgrade Sequence +1. **Start with Independent Libraries:** Least dependent class libraries first. +2. **Next:** Shared components and common utilities. +3. **Then:** API, Web, or Function projects. +4. **Finally:** Tests, integration points, and pipelines. + +**Chat Prompt:** +> "Generate the optimal upgrade order for this repository, prioritizing least-dependent projects first." + +--- + +## Per-Project Upgrade Flow +1. **Create branch:** `upgrade/-to-` +2. **Edit ``** in `.csproj` to the suggested version (e.g., `net9.0`) +3. **Restore & update packages:** + ```bash + dotnet restore + dotnet list package --outdated + dotnet add package --version + ``` +4. **Build & test:** + ```bash + dotnet build .csproj + dotnet test .Tests.csproj + ``` +5. **Fix issues** — resolve deprecated APIs, adjust configurations, modernize JSON/logging/DI. +6. **Commit & push** PR with test evidence and checklist. + +--- + +## Breaking Changes & Modernization +- Use `.NET Upgrade Assistant` for initial recommendations. +- Apply analyzers to detect obsolete APIs. +- Replace outdated SDKs (e.g., `Microsoft.Azure.*` → `Azure.*`). +- Modernize startup logic (`Startup.cs` → `Program.cs` top-level statements). + +**Chat Prompt:** +> "List deprecated or incompatible APIs when upgrading from to for ." + +--- + +## CI/CD Configuration Updates +Ensure pipelines use the detected **target version** dynamically: + +**Azure DevOps** +```yaml +- task: UseDotNet@2 + inputs: + packageType: 'sdk' + version: '$(TargetDotNetVersion).x' +``` + +**GitHub Actions** +```yaml +- uses: actions/setup-dotnet@v4 + with: + dotnet-version: '${{ env.TargetDotNetVersion }}.x' +``` + +--- + +## Validation Checklist +- [ ] TargetFramework upgraded to next stable version +- [ ] All NuGet packages compatible and updated +- [ ] Build and test pipelines succeed locally and in CI +- [ ] Integration tests pass +- [ ] Deployed to a lower environment and verified + +--- + +## Branching & Rollback Strategy +- Use feature branches: `upgrade/-to-` +- Commit frequently and keep changes atomic +- If CI fails after merge, revert PR and isolate failing modules + +**Chat Prompt:** +> "Suggest a rollback and validation plan if the .NET upgrade for introduces build or runtime regressions." + +--- + +## Automation & Scaling +- Automate upgrade detection with GitHub Actions or Azure Pipelines. +- Schedule nightly runs to check for new .NET releases via `dotnet --list-sdks`. +- Use agents to automatically raise PRs for outdated frameworks. + +--- + +## Chatmode Prompt Library +1. "List all projects with current and recommended .NET versions." +2. "Generate a per-project upgrade plan from to ." +3. "Suggest .csproj and pipeline edits to upgrade ." +4. "Summarize build/test results post-upgrade for ." +5. "Create PR description and checklist for the upgrade." + +--- + +_End of chatmode playbook — adaptive across any .NET version. Detects the current repo version and provides upgrade paths, scripts, and validation steps dynamically._ From f40cc7e22e1bd4ea1c1f150ad1dbf1b7f49f2782 Mon Sep 17 00:00:00 2001 From: kshashank57 <57212456+kshashank57@users.noreply.github.com> Date: Fri, 17 Oct 2025 12:00:56 +0530 Subject: [PATCH 4/7] Enhance .NET Upgrade Chatmode Guidance Updated .NET upgrade chatmode guidance with detailed instructions and tools for project migration and modernization. --- ...chatmode.md => dotnet-upgrade.chatmode.md} | 69 +++++++++++++++++-- 1 file changed, 65 insertions(+), 4 deletions(-) rename chatmodes/{dotnet_upgrade_chatmode.md => dotnet-upgrade.chatmode.md} (69%) diff --git a/chatmodes/dotnet_upgrade_chatmode.md b/chatmodes/dotnet-upgrade.chatmode.md similarity index 69% rename from chatmodes/dotnet_upgrade_chatmode.md rename to chatmodes/dotnet-upgrade.chatmode.md index 89a7251e..fe6472c3 100644 --- a/chatmodes/dotnet_upgrade_chatmode.md +++ b/chatmodes/dotnet-upgrade.chatmode.md @@ -1,6 +1,69 @@ -# .NET Upgrade — Chatmode Guidance +--- +description: 'Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.' +tools: ['codebase', 'edit/editFiles', 'search', 'runCommands', 'runTasks', 'runTests', 'problems', 'changes', 'usages', 'findTestFiles', 'testFailure', 'terminalLastCommand', 'terminalSelection', 'fetch', 'microsoft.docs.mcp'] +--- + +# .NET Upgrade Collection + +.NET Framework upgrade specialist for comprehensive project migration + +**Tags:** dotnet, upgrade, migration, framework, modernization + +## Collection Usage + +### .NET Upgrade Chat Mode + +Discover and plan your .NET upgrade journey! + +```markdown, upgrade-analysis.prompt.md +--- +mode: dotnet-upgrade +title: Analyze current .NET framework versions and create upgrade plan +--- +Analyze the repository and list each project's current TargetFramework +along with the latest available LTS version from Microsoft's release schedule. +Create an upgrade strategy prioritizing least-dependent projects first. +``` + +The upgrade chat mode automatically adapts to your repository's current .NET version and provides context-aware upgrade guidance to the next stable version. -> **Purpose:** A generic, ChatGPT-first (chatmode) playbook to discover, plan, execute, and validate .NET upgrades for any multi-project solution. This version automatically adapts to the repository’s current .NET version and provides context-aware upgrade guidance to the next stable version. +It will help you: +- Auto-detect current .NET versions across all projects +- Generate optimal upgrade sequences +- Identify breaking changes and modernization opportunities +- Create per-project upgrade flows + +--- + +### .NET Upgrade Instructions + +Execute comprehensive .NET framework upgrades with structured guidance! + +The instructions provide: +- Sequential upgrade strategies +- Dependency analysis and sequencing +- Framework targeting and code adjustments +- NuGet and dependency management +- CI/CD pipeline updates +- Testing and validation procedures + +Use these instructions when implementing upgrade plans to ensure proper execution and validation. + +--- + +### .NET Upgrade Prompts + +Quick access to specialized upgrade analysis prompts! + +The prompts collection includes ready-to-use queries for: +- Project discovery and assessment +- Upgrade strategy and sequencing +- Framework targeting and code adjustments +- Breaking change analysis +- CI/CD pipeline updates +- Final validation and delivery + +Use these prompts for targeted analysis of specific upgrade aspects. --- @@ -157,5 +220,3 @@ Ensure pipelines use the detected **target version** dynamically: 5. "Create PR description and checklist for the upgrade." --- - -_End of chatmode playbook — adaptive across any .NET version. Detects the current repo version and provides upgrade paths, scripts, and validation steps dynamically._ From 4357dd1f5234d34f5263263ce4f5c6e10a67d835 Mon Sep 17 00:00:00 2001 From: kshashank57 <57212456+kshashank57@users.noreply.github.com> Date: Fri, 17 Oct 2025 12:05:09 +0530 Subject: [PATCH 5/7] Revise .NET upgrade instructions and agent prompt Updated the instructions for .NET Framework upgrades to include a name and description for the specialized agent, and refined the prompt example for clarity. --- ...ctions.md => dotnet-upgrade.instructions.md} | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) rename instructions/{dotnet-upgrade-instructions.md => dotnet-upgrade.instructions.md} (93%) diff --git a/instructions/dotnet-upgrade-instructions.md b/instructions/dotnet-upgrade.instructions.md similarity index 93% rename from instructions/dotnet-upgrade-instructions.md rename to instructions/dotnet-upgrade.instructions.md index 1d605472..e384dc37 100644 --- a/instructions/dotnet-upgrade-instructions.md +++ b/instructions/dotnet-upgrade.instructions.md @@ -1,4 +1,9 @@ -You are an **specialized agent** for upgrades of .NET Framework please keep going until the desired frameworks upgrade are completely resolved, tested using the instructions below before ending your turn and yielding back to the user. +--- +name: ".NET Framework Upgrade Specialist" +description: "Specialized agent for comprehensive .NET framework upgrades with progressive tracking and validation" +--- + +You are a **specialized agent** for upgrades of .NET Framework. Please keep going until the desired frameworks upgrade are completely resolved, tested using the instructions below before ending your turn and yielding back to the user. Your thinking should be thorough and so it's fine if it's very long. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough. @@ -273,8 +278,10 @@ For organizations with multiple repositories: - **Incremental Upgrades** Large solutions may require upgrading one project at a time. -### ✅ Example Agent Prompt + ### ✅ Example Agent Prompt -> Upgrade this repository to the latest supported .NET version following the steps in `dotnet-upgrade-instructions.md`. -> Detect project type (.NET Core, Standard, or Framework) and apply the correct migration path. -> Ensure all tests pass and CI/CD workflows are updated. + > Upgrade this repository to the latest supported .NET version following the steps in `dotnet-upgrade-instructions.md`. + > Detect project type (.NET Core, Standard, or Framework) and apply the correct migration path. + > Ensure all tests pass and CI/CD workflows are updated. + +--- From 921b111ed897ce71739a42e3c849b38fc699d7ba Mon Sep 17 00:00:00 2001 From: kshashank57 <57212456+kshashank57@users.noreply.github.com> Date: Fri, 17 Oct 2025 12:07:23 +0530 Subject: [PATCH 6/7] Revise .NET Upgrade Prompts for clarity and completeness 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. --- prompts/dotnet-upgrade-prompts.md | 86 ---------------------- prompts/dotnet-upgrade.prompts.md | 116 ++++++++++++++++++++++++++++++ 2 files changed, 116 insertions(+), 86 deletions(-) delete mode 100644 prompts/dotnet-upgrade-prompts.md create mode 100644 prompts/dotnet-upgrade.prompts.md diff --git a/prompts/dotnet-upgrade-prompts.md b/prompts/dotnet-upgrade-prompts.md deleted file mode 100644 index 6422a75b..00000000 --- a/prompts/dotnet-upgrade-prompts.md +++ /dev/null @@ -1,86 +0,0 @@ -# .NET Upgrade Prompts - -## Purpose -Prompts for analyzing, planning, executing, and validating framework upgrades for multi-project .NET solutions — including .NET Core, .NET Framework, and .NET Standard migrations. - -## Prompts - -### Project Discovery & Assessment -- Identify all projects in the solution and classify them by type (`.NET Framework`, `.NET Core`, `.NET Standard`). -- Analyze each `.csproj` for its current `TargetFramework` and SDK usage. -- Review external and internal dependencies for framework compatibility. -- Determine the upgrade complexity based on dependency graph depth. -- Identify legacy `packages.config` projects needing migration to `PackageReference`. - -### Upgrade Strategy & Sequencing -- Recommend a project upgrade order from least to most dependent components. -- Suggest how to isolate class library upgrades before API or Azure Function migrations. -- Propose an incremental upgrade strategy with rollback checkpoints. -- Evaluate the use of **Upgrade Assistant** or **manual upgrades** based on project structure. -- Generate an upgrade checklist for tracking build, test, and deployment readiness. - -### Framework Targeting & Code Adjustments -- Suggest the correct `TargetFramework` for each project (e.g., `net8.0`). -- Review and update deprecated SDK or build configurations. -- Identify code patterns needing modernization (e.g., `WebHostBuilder` → `HostBuilder`). -- Suggest replacements for deprecated .NET APIs and third-party libraries. -- Recommend conversion of synchronous calls to async where appropriate. - -### NuGet & Dependency Management -- Analyze outdated or incompatible NuGet packages and suggest compatible versions. -- Identify third-party libraries that lack .NET 8 support and provide migration paths. -- Recommend strategies for handling shared dependency upgrades across projects. -- Evaluate usage of legacy packages and suggest alternatives in Microsoft-supported namespaces. -- Review transitive dependencies and potential version conflicts after upgrade. - -### CI/CD & Build Pipeline Updates -- Analyze YAML build definitions for SDK version pinning and recommend updates. -- Suggest modifications for `UseDotNet@2` and `NuGetToolInstaller` tasks. -- Generate updated build pipeline snippets for .NET 8 migration. -- Recommend validation builds on feature branches before merging to main. -- Identify opportunities to automate test and build verification in CI pipelines. - -### Testing & Validation -- Propose validation checks to ensure the upgraded solution builds and runs successfully. -- Recommend automated test execution for unit and integration suites post-upgrade. -- Generate prompts to verify logging, telemetry, and service connectivity. -- Suggest strategies for verifying backward compatibility and runtime behavior. -- Recommend UAT deployment verification steps before production rollout. - -### Breaking Change Analysis -- Identify deprecated APIs or removed namespaces between target versions. -- Suggest automated scanning using `.NET Upgrade Assistant` and API Analyzer. -- Recommend replacement APIs or libraries for known breaking areas. -- Review configuration changes such as `Startup.cs` → `Program.cs` refactoring. -- Suggest regression testing prompts focused on upgraded API endpoints or services. - -### Version Control & Commit Strategy -- Recommend branching strategy for safe upgrade with rollback capability. -- Generate commit templates for partial and complete project upgrades. -- Suggest best practices for creating structured PRs (`Upgrade to .NET [Version]`). -- Identify tagging strategies for PRs involving breaking changes. -- Recommend peer review focus areas (build, test, and dependency validation). - -### Documentation & Communication -- Suggest how to document each project’s framework change in the PR. -- Propose automated release note generation summarizing upgrades and test results. -- Recommend communicating version upgrades and migration timelines to consumers. -- Generate documentation prompts for dependency updates and validation results. -- Suggest maintaining an upgrade summary dashboard or markdown checklist. - -### Tools & Automation -- Recommend when and how to use: - - `.NET Upgrade Assistant` - - `dotnet list package --outdated` - - `dotnet migrate` - - `graph.json` dependency visualization -- Generate scripts or prompts for analyzing dependency graphs before upgrading. -- Propose AI-assisted prompts for Copilot to identify upgrade issues automatically. -- Suggest how to validate automation output across multiple repositories. - -### Final Validation & Delivery -- Generate prompts to confirm the final upgraded solution passes all validation checks. -- Suggest production deployment verification steps post-upgrade. -- Recommend generating final test results and build artifacts. -- Create a checklist summarizing completion across projects (builds/tests/deployment). -- Generate a release note summarizing framework changes and CI/CD updates. diff --git a/prompts/dotnet-upgrade.prompts.md b/prompts/dotnet-upgrade.prompts.md new file mode 100644 index 00000000..f20ebf9f --- /dev/null +++ b/prompts/dotnet-upgrade.prompts.md @@ -0,0 +1,116 @@ +--- +name: ".NET Upgrade Analysis Prompts" +description: "Ready-to-use prompts for comprehensive .NET framework upgrade analysis and execution" +prompts: +--- + # Project Discovery & Assessment + - name: "Project Classification Analysis" + prompt: "Identify all projects in the solution and classify them by type (`.NET Framework`, `.NET Core`, `.NET Standard`). Analyze each `.csproj` for its current `TargetFramework` and SDK usage." + + - name: "Dependency Compatibility Review" + prompt: "Review external and internal dependencies for framework compatibility. Determine the upgrade complexity based on dependency graph depth." + + - name: "Legacy Package Detection" + prompt: "Identify legacy `packages.config` projects needing migration to `PackageReference` format." + + # Upgrade Strategy & Sequencing + - name: "Project Upgrade Ordering" + prompt: "Recommend a project upgrade order from least to most dependent components. Suggest how to isolate class library upgrades before API or Azure Function migrations." + + - name: "Incremental Strategy Planning" + prompt: "Propose an incremental upgrade strategy with rollback checkpoints. Evaluate the use of **Upgrade Assistant** or **manual upgrades** based on project structure." + + - name: "Progress Tracking Setup" + prompt: "Generate an upgrade checklist for tracking build, test, and deployment readiness across all projects." + + # Framework Targeting & Code Adjustments + - name: "Target Framework Selection" + prompt: "Suggest the correct `TargetFramework` for each project (e.g., `net8.0`). Review and update deprecated SDK or build configurations." + + - name: "Code Modernization Analysis" + prompt: "Identify code patterns needing modernization (e.g., `WebHostBuilder` → `HostBuilder`). Suggest replacements for deprecated .NET APIs and third-party libraries." + + - name: "Async Pattern Conversion" + prompt: "Recommend conversion of synchronous calls to async where appropriate for improved performance and scalability." + + # NuGet & Dependency Management + - name: "Package Compatibility Analysis" + prompt: "Analyze outdated or incompatible NuGet packages and suggest compatible versions. Identify third-party libraries that lack .NET 8 support and provide migration paths." + + - name: "Shared Dependency Strategy" + prompt: "Recommend strategies for handling shared dependency upgrades across projects. Evaluate usage of legacy packages and suggest alternatives in Microsoft-supported namespaces." + + - name: "Transitive Dependency Review" + prompt: "Review transitive dependencies and potential version conflicts after upgrade. Suggest resolution strategies for dependency conflicts." + + # CI/CD & Build Pipeline Updates + - name: "Pipeline Configuration Analysis" + prompt: "Analyze YAML build definitions for SDK version pinning and recommend updates. Suggest modifications for `UseDotNet@2` and `NuGetToolInstaller` tasks." + + - name: "Build Pipeline Modernization" + prompt: "Generate updated build pipeline snippets for .NET 8 migration. Recommend validation builds on feature branches before merging to main." + + - name: "CI Automation Enhancement" + prompt: "Identify opportunities to automate test and build verification in CI pipelines. Suggest strategies for continuous integration validation." + + # Testing & Validation + - name: "Build Validation Strategy" + prompt: "Propose validation checks to ensure the upgraded solution builds and runs successfully. Recommend automated test execution for unit and integration suites post-upgrade." + + - name: "Service Integration Verification" + prompt: "Generate validation steps to verify logging, telemetry, and service connectivity. Suggest strategies for verifying backward compatibility and runtime behavior." + + - name: "Deployment Readiness Check" + prompt: "Recommend UAT deployment verification steps before production rollout. Create comprehensive testing scenarios for upgraded components." + + # Breaking Change Analysis + - name: "API Deprecation Detection" + prompt: "Identify deprecated APIs or removed namespaces between target versions. Suggest automated scanning using `.NET Upgrade Assistant` and API Analyzer." + + - name: "API Replacement Strategy" + prompt: "Recommend replacement APIs or libraries for known breaking areas. Review configuration changes such as `Startup.cs` → `Program.cs` refactoring." + + - name: "Regression Testing Focus" + prompt: "Suggest regression testing scenarios focused on upgraded API endpoints or services. Create test plans for critical functionality validation." + + # Version Control & Commit Strategy + - name: "Branching Strategy Planning" + prompt: "Recommend branching strategy for safe upgrade with rollback capability. Generate commit templates for partial and complete project upgrades." + + - name: "PR Structure Optimization" + prompt: "Suggest best practices for creating structured PRs (`Upgrade to .NET [Version]`). Identify tagging strategies for PRs involving breaking changes." + + - name: "Code Review Guidelines" + prompt: "Recommend peer review focus areas (build, test, and dependency validation). Create checklists for effective upgrade reviews." + + # Documentation & Communication + - name: "Upgrade Documentation Strategy" + prompt: "Suggest how to document each project's framework change in the PR. Propose automated release note generation summarizing upgrades and test results." + + - name: "Stakeholder Communication" + prompt: "Recommend communicating version upgrades and migration timelines to consumers. Generate documentation templates for dependency updates and validation results." + + - name: "Progress Tracking Systems" + prompt: "Suggest maintaining an upgrade summary dashboard or markdown checklist. Create templates for tracking upgrade progress across multiple projects." + + # Tools & Automation + - name: "Upgrade Tool Selection" + prompt: "Recommend when and how to use: `.NET Upgrade Assistant`, `dotnet list package --outdated`, `dotnet migrate`, and `graph.json` dependency visualization." + + - name: "Analysis Script Generation" + prompt: "Generate scripts or prompts for analyzing dependency graphs before upgrading. Propose AI-assisted prompts for Copilot to identify upgrade issues automatically." + + - name: "Multi-Repository Validation" + prompt: "Suggest how to validate automation output across multiple repositories. Create standardized validation workflows for enterprise-scale upgrades." + + # Final Validation & Delivery + - name: "Final Solution Validation" + prompt: "Generate validation steps to confirm the final upgraded solution passes all validation checks. Suggest production deployment verification steps post-upgrade." + + - name: "Deployment Readiness Confirmation" + prompt: "Recommend generating final test results and build artifacts. Create a checklist summarizing completion across projects (builds/tests/deployment)." + + - name: "Release Documentation" + prompt: "Generate a release note summarizing framework changes and CI/CD updates. Create comprehensive upgrade summary documentation." + +--- From 3abe2515720e8060d9731376d75286c070b0f457 Mon Sep 17 00:00:00 2001 From: Shashank Konjarla Date: Tue, 21 Oct 2025 08:34:41 +0530 Subject: [PATCH 7/7] Updating README instructions --- README.chatmodes.md | 1 + README.collections.md | 2 +- README.instructions.md | 1 + 3 files changed, 3 insertions(+), 1 deletion(-) diff --git a/README.chatmodes.md b/README.chatmodes.md index 264ae8e4..e706cfcb 100644 --- a/README.chatmodes.md +++ b/README.chatmodes.md @@ -14,6 +14,7 @@ Custom chat modes define specific behaviors and tools for GitHub Copilot Chat, e | Title | Description | | ----- | ----------- | +| [.NET Upgrade Collection](chatmodes/dotnet-upgrade.chatmode.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fdotnet-upgrade.chatmode.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fdotnet-upgrade.chatmode.md) | Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation. | | [4.1 Beast Mode (VS Code v1.102)](chatmodes/4.1-Beast.chatmode.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2F4.1-Beast.chatmode.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2F4.1-Beast.chatmode.md) | GPT 4.1 as a top-notch coding agent. | | [Accessibility mode](chatmodes/accesibility.chatmode.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Faccesibility.chatmode.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Faccesibility.chatmode.md) | Accessibility mode. | | [API Architect mode instructions](chatmodes/api-architect.chatmode.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/chatmode?url=vscode%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fapi-architect.chatmode.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/chatmode?url=vscode-insiders%3Achat-mode%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fchatmodes%2Fapi-architect.chatmode.md) | Your role is that of an API architect. Help mentor the engineer by providing guidance, support, and working code. | diff --git a/README.collections.md b/README.collections.md index 11a5e778..f4cc19ed 100644 --- a/README.collections.md +++ b/README.collections.md @@ -32,7 +32,7 @@ Curated collections of related prompts, instructions, and chat modes organized a | [Project Planning & Management](collections/project-planning.md) | Tools and guidance for software project planning, feature breakdown, epic management, implementation planning, and task organization for development teams. | 17 items | planning, project-management, epic, feature, implementation, task, architecture, technical-spike | | [Python MCP Server Development](collections/python-mcp-development.md) | Complete toolkit for building Model Context Protocol (MCP) servers in Python using the official SDK with FastMCP. Includes instructions for best practices, a prompt for generating servers, and an expert chat mode for guidance. | 3 items | python, mcp, model-context-protocol, fastmcp, server-development | | [Ruby MCP Server Development](collections/ruby-mcp-development.md) | 'Complete toolkit for building Model Context Protocol servers in Ruby using the official MCP Ruby SDK gem with Rails integration support.' | 3 items | ruby, mcp, model-context-protocol, server-development, sdk, rails, gem | -| [Rust MCP Server Development](collections/rust-mcp-development.md) | 'Build high-performance Model Context Protocol servers in Rust using the official rmcp SDK with async/await, procedural macros, and type-safe implementations.' | 3 items | rust, mcp, model-context-protocol, server-development, sdk, tokio, async, macros, rmcp | +| [Rust MCP Server Development](collections/rust-mcp-development.md) | Build high-performance Model Context Protocol servers in Rust using the official rmcp SDK with async/await, procedural macros, and type-safe implementations. | 3 items | rust, mcp, model-context-protocol, server-development, sdk, tokio, async, macros, rmcp | | [Security & Code Quality](collections/security-best-practices.md) | Security frameworks, accessibility guidelines, performance optimization, and code quality best practices for building secure, maintainable, and high-performance applications. | 6 items | security, accessibility, performance, code-quality, owasp, a11y, optimization, best-practices | | [Swift MCP Server Development](collections/swift-mcp-development.md) | 'Comprehensive collection for building Model Context Protocol servers in Swift using the official MCP Swift SDK with modern concurrency features.' | 3 items | swift, mcp, model-context-protocol, server-development, sdk, ios, macos, concurrency, actor, async-await | | [Tasks by microsoft/edge-ai](collections/edge-ai-tasks.md) | Task Researcher and Task Planner for intermediate to expert users and large codebases - Brought to you by microsoft/edge-ai | 3 items | architecture, planning, research, tasks, implementation | diff --git a/README.instructions.md b/README.instructions.md index ba4cf1b1..7678957a 100644 --- a/README.instructions.md +++ b/README.instructions.md @@ -16,6 +16,7 @@ Team and project-specific instructions to enhance GitHub Copilot's behavior for | ----- | ----------- | | [.NET Framework Development](instructions/dotnet-framework.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdotnet-framework.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdotnet-framework.instructions.md) | Guidance for working with .NET Framework projects. Includes project structure, C# language version, NuGet management, and best practices. | | [.NET MAUI](instructions/dotnet-maui.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdotnet-maui.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdotnet-maui.instructions.md) | .NET MAUI component and application patterns | +| [.NET Project Upgrade Instructions](instructions/dotnet-upgrade.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdotnet-upgrade.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdotnet-upgrade.instructions.md) | Specialized agent for comprehensive .NET framework upgrades with progressive tracking and validation | | [AI Prompt Engineering & Safety Best Practices](instructions/ai-prompt-engineering-safety-best-practices.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fai-prompt-engineering-safety-best-practices.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fai-prompt-engineering-safety-best-practices.instructions.md) | Comprehensive best practices for AI prompt engineering, safety frameworks, bias mitigation, and responsible AI usage for Copilot and LLMs. | | [Angular Development Instructions](instructions/angular.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fangular.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fangular.instructions.md) | Angular-specific coding standards and best practices | | [Ansible Conventions and Best Practices](instructions/ansible.instructions.md)
[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fansible.instructions.md)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fansible.instructions.md) | Ansible conventions and best practices |