원클릭으로 Manus에서 모든 스킬 실행

dotnet-sdk-style-upgrade

스타3

포크0

업데이트2026년 3월 18일 20:56

**WORKFLOW SKILL** — Convert legacy .NET project files (.csproj, .fsproj, .vbproj) to modern SDK-style format. WHEN: "modernize .NET project", "upgrade csproj to SDK-style", "migrate to SDK-style project", "convert legacy .NET project", "non-SDK-style project upgrade". INVOKES: file system tools for project file analysis. FOR SINGLE OPERATIONS: Edit the project file XML directly.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

PlagueHO

PlagueHO/plagueho.skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Upgrading to SDK-Style Projects

Required Reference: Before proceeding, consult the .NET SDK-style project documentation for authoritative guidance on SDK-style projects.

SDK Selection Guide

Analyze project files to recommend the appropriate SDK:

Project Type	SDK	Indicators
Console/Library	`Microsoft.NET.Sdk`	No web/UI references
ASP.NET Core/Web API	`Microsoft.NET.Sdk.Web`	`Microsoft.AspNetCore.*`, Startup.cs, Controllers
Razor Class Library	`Microsoft.NET.Sdk.Razor`	`.razor` files, Razor components
Blazor WebAssembly	`Microsoft.NET.Sdk.BlazorWebAssembly`	`Microsoft.AspNetCore.Components.WebAssembly`
Worker/Background Service	`Microsoft.NET.Sdk.Worker`	`IHostedService`, BackgroundService
WinForms	`Microsoft.NET.Sdk` + `<UseWindowsForms>`	`System.Windows.Forms`
WPF	`Microsoft.NET.Sdk` + `<UseWPF>`	`PresentationFramework`, `.xaml` files
MSTest	`MSTest.Sdk`	`Microsoft.VisualStudio.TestTools.UnitTesting`
.NET Aspire AppHost	`Aspire.AppHost.Sdk`	Aspire orchestration project

Analysis Checklist

Before upgrading, analyze and review:

Upgrade Process

Identify SDK: Analyze references and file patterns to determine SDK

Create minimal project file:

<Project Sdk="SELECTED_SDK">
  <PropertyGroup>
    <TargetFramework>net9.0</TargetFramework>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
  </PropertyGroup>
</Project>

Add OutputType if executable: <OutputType>Exe</OutputType> or <OutputType>WinExe</OutputType>
Migrate PackageReferences: Convert packages.config or HintPath references
Remove redundant elements: SDK-style auto-includes *.cs, *.resx, etc.

Add desktop properties for WinForms/WPF:

<UseWindowsForms>true</UseWindowsForms>
<!-- or -->
<UseWPF>true</UseWPF>

Key Differences from Legacy

No <Compile Include="**/*.cs" /> needed (auto-included)
No assembly info file needed (<GenerateAssemblyInfo>true</GenerateAssemblyInfo> default)
PackageReference replaces packages.config
No ProjectGuid, ProjectTypeGuids required
No explicit SDK imports needed

Validation

After upgrade, run:

dotnet build
dotnet msbuild -preprocess:output.xml  # View expanded project

이 저장소의 다른 Skills

같은 저장소

upgrade-pester-v4-to-v5

PlagueHO/plagueho.skills

**WORKFLOW SKILL** — Migrate PowerShell Pester v4 tests to Pester v5, covering structural, assertion, and mock changes. WHEN: "upgrade Pester to v5", "migrate Pester v4 to v5", "convert Pester tests to Pester 5", "modernize Pester tests", "Assert-MockCalled to Should -Invoke". INVOKES: run_in_terminal for detection scripts and Invoke-Pester. FOR SINGLE OPERATIONS: edit one assertion or Invoke-Pester call directly.

2026-07-033

update-avm-modules

PlagueHO/plagueho.skills

**WORKFLOW SKILL** — Update Azure Verified Modules (AVM) to their latest versions in Bicep files. Scans for AVM module references, queries the Microsoft Container Registry (MCR) for latest versions, compares using semantic versioning, reviews breaking changes, and applies updates with validation. WHEN: 'update AVM', 'update Bicep modules', 'latest AVM versions', 'update Azure Verified Modules', 'upgrade Bicep dependencies', 'check AVM versions', 'update module versions'. INVOKES: run_in_terminal for MCR API queries and bicep lint. FOR SINGLE OPERATIONS: Use az bicep build to validate individual files.

2026-06-053

create-microsoft-research-plan

PlagueHO/plagueho.skills

**WORKFLOW SKILL** — Generate a structured research plan for a Microsoft technology topic, defining scope, research areas, search terms, and output section mapping based on purpose (guide/presentation/lab/demo). WHEN: "create research plan", "plan Microsoft research", "research plan for", "plan technical research", "scope research topic", "define research areas". INVOKES: editFiles. FOR SINGLE OPERATIONS: Create plan.md manually.

2026-05-113

initiate-microsoft-researcher

PlagueHO/plagueho.skills

**WORKFLOW SKILL** — Mandatory entry point for all research projects. Validates topic, confirms the plan with the user, scaffolds the folder structure, and initializes the research log before any subagent work begins. This skill is ONLY invoked by the research-microsoft-technology orchestrator agent. INVOKES: create-microsoft-research-plan, research-output-scaffolding, vscode_askQuestions. FOR SINGLE OPERATIONS: Not applicable — this skill must always be used to start research.

2026-05-113

research-note-template

PlagueHO/plagueho.skills

**WORKFLOW SKILL** — Extract structured research notes from a source URL or document into a standardized YAML-frontmatter markdown note. Applies fixed extraction rules for consistent note-taking across all research areas. WHEN: "create research note", "extract research note", "note from URL", "research note template", "take research notes", "extract findings from". INVOKES: microsoft_docs_search, microsoft_docs_fetch, fetch_webpage, editFiles. FOR SINGLE OPERATIONS: Copy the note template and fill manually.

2026-05-113

research-output-scaffolding

PlagueHO/plagueho.skills

**WORKFLOW SKILL** — Scaffold the .research/ output folder structure for a research topic, creating note directories per area, log files, and output section placeholders based on the research plan. WHEN: "scaffold research output", "create research folder", "initialize research directory", "set up research workspace", "research output structure", "scaffold .research folder". INVOKES: run_in_terminal for scaffolding scripts. FOR SINGLE OPERATIONS: Create directories manually.

2026-05-083

name	dotnet-sdk-style-upgrade
description	WORKFLOW SKILL — Convert legacy .NET project files (.csproj, .fsproj, .vbproj) to modern SDK-style format. WHEN: "modernize .NET project", "upgrade csproj to SDK-style", "migrate to SDK-style project", "convert legacy .NET project", "non-SDK-style project upgrade". INVOKES: file system tools for project file analysis. FOR SINGLE OPERATIONS: Edit the project file XML directly.
metadata	{"author":"microsoft-foundry-jumpstart","version":"1.0","reference":"https://learn.microsoft.com/en-us/dotnet/core/project-sdk/overview"}

name	dotnet-sdk-style-upgrade
description	WORKFLOW SKILL — Convert legacy .NET project files (.csproj, .fsproj, .vbproj) to modern SDK-style format. WHEN: "modernize .NET project", "upgrade csproj to SDK-style", "migrate to SDK-style project", "convert legacy .NET project", "non-SDK-style project upgrade". INVOKES: file system tools for project file analysis. FOR SINGLE OPERATIONS: Edit the project file XML directly.
metadata	{"author":"microsoft-foundry-jumpstart","version":"1.0","reference":"https://learn.microsoft.com/en-us/dotnet/core/project-sdk/overview"}