managing-legacy-dotnet-packages Skill
Manages NuGet packages in old-style .NET Framework projects (.NET Framework 4.x). Handles both packages.config (classic NuGet) and PackageReference in non-SDK-style csproj files. Use when updating, adding, or removing NuGet packages in projects that use packages.config, have old-style csproj format (ToolsVersion attrib Published by microsoft in upgrade-agent-plugins.
What is managing-legacy-dotnet-packages Skill?
Manages NuGet packages in old-style .NET Framework projects (.NET Framework 4.x). Handles both packages.config (classic NuGet) and PackageReference in non-SDK-style csproj files. Use when updating, adding, or removing NuGet packages in projects that use packages.config, have old-style csproj format (ToolsVersion attrib Published by microsoft in upgrade-agent-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using upgrade-agent-plugins
Technical details
- Install or run with Copy skill directory
When to use managing-legacy-dotnet-packages Skill
- Use it for developers using upgrade-agent-plugins.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/upgrade-agent-plugins
- Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/common/managing-legacy-dotnet-packages/SKILL.md
What it does
Manages NuGet packages in old-style .NET Framework projects (.NET Framework 4.x). Handles both packages.config (classic NuGet) and PackageReference in non-SDK-style csproj files. Use when updating, adding, or removing NuGet packages in projects that use packages.config, have old-style csproj format (ToolsVersion attrib
Skill instructions
Legacy .NET Framework Package Management Overview Manage NuGet packages in old-style .NET Framework projects where packages use packages.config (classic NuGet format) or PackageReference in non-SDK-style csproj files. This skill is different from managing-package-references which handles SDK-style projects with PackageReference and Central Package Management (CPM). Legacy .NET Framework projects have different package management mechanics. Detecting Package Management Format Before modifying packages, determine which format the project uses: | Indicator | Format | Management Approach | |-----------|--------|-------------------| | packages.config file in project directory | Classic NuGet | Edit packages.config XML + update HintPath in csproj | | <PackageReference in csproj WITHOUT Sdk attribute on <Project | PackageReference in old-style | Edit version in csproj XML directly | | <Reference with <HintPath containing packages\ path | Classic NuGet (assembly reference) | Update HintPath wh
Explore related resources
Frequently asked questions
What is managing-legacy-dotnet-packages?
managing-legacy-dotnet-packages is a open-source AI agent skill with Copy skill directory. Manages NuGet packages in old-style .NET Framework projects (.NET Framework 4.x). Handles both packages.config (classic NuGet) and PackageReference in non-SDK-style csproj files.
Who is managing-legacy-dotnet-packages best for?
managing-legacy-dotnet-packages is best for reusing agent instructions, scripts, and references.
How do I install managing-legacy-dotnet-packages?
Install or run managing-legacy-dotnet-packages using Copy skill directory. Check managing-legacy-dotnet-packages for the latest setup command.
Is managing-legacy-dotnet-packages actively maintained?
managing-legacy-dotnet-packages may need a closer maintenance check before production use.
Auto-fetched from GitHub.
