vssdk-sdk-style-conversion

Convert legacy VSIX/VSSDK projects to SDK-style format.

19|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill vssdk-sdk-style-conversion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vssdk-sdk-style-conversion
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/scenarios/vssdk-sdk-style-conversion
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill vssdk-sdk-style-conversion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Microsoft.NET.Sdk, Microsoft.VSSDK.BuildTools, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the challenge of converting legacy Visual Studio extension (VSIX/VSSDK) projects to the modern SDK-style format, ensuring compatibility with contemporary development practices.

Core Features & Use Cases

  • Legacy to SDK Conversion: Converts project formats from legacy to SDK-style, supporting Visual Studio extensions.
  • VSSDK Specifics: Handles package references, VSIX manifest, VSCT command tables, and project capabilities.
  • Use Case: Ideal for developers tasked with modernizing an existing VSIX/VSSDK project, ensuring it supports newer Visual Studio versions and frameworks.

Quick Start

Run the skill to convert your VSIX/VSSDK project to the SDK-style format.

Frequently Asked Questions about vssdk-sdk-style-conversion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a legacy VSIX project to SDK-style format?

This Skill converts legacy VSIX projects to SDK-style format by automating the migration of project files, VSSDK-specific configurations, package references, and VSIX manifests to ensure compatibility with modern Visual Studio versions.

What is SDK-style conversion for Visual Studio extensions?

SDK-style conversion for Visual Studio extensions modernizes legacy VSIX/VSSDK projects by migrating them to the current .NET SDK project format, streamlining dependency management and ensuring compatibility with contemporary development frameworks.

Do I need VSSDK Build Tools to modernize a VSIX project?

Yes, modernizing a VSIX project to SDK-style requires the VSSDK Build Tools and the .NET SDK installed in your development environment to successfully convert and build the extension.

Can I use SDK-style conversion for VSCT command tables and project capabilities?

Yes, SDK-style conversion handles VSSDK-specific configurations including VSCT command tables, project capabilities, VSIX manifests, and package references to ensure full extension compatibility during the modernization process.

When should I migrate my VSSDK project to the .NET SDK format?

You should migrate your VSSDK project to the .NET SDK format when modernizing an existing Visual Studio extension to support newer Visual Studio versions, leverage contemporary frameworks, and adopt streamlined package reference practices.