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 attribute), or target .NET Framework without SDK-style project format. Also triggers for "nuget update", "packages.config", "update package in old project", or "HintPath" tasks.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
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 attribute), or target .NET Framework without SDK-style project format. Also triggers for "nuget update", "packages.config", "update package in old project", or "HintPath" tasks.
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 when package version changes
No packages.config AND no PackageReference
No NuGet packages
Nothing to manage
Quick Detection Steps
Check for packages.config in the project directory.
If not found, check csproj for <PackageReference> elements.
Check if csproj root is <Project Sdk="..."> (SDK-style) or <Project ToolsVersion="..."> (old-style).
Workflow: packages.config Projects
Understanding packages.config
packages.config is an XML file listing all NuGet packages and their versions:
Also update targetFramework to net481 if upgrading the project TFM.
Update <HintPath> in csproj: The HintPath contains the version number in the path.
<!-- Before --><HintPath>..\packages\Newtonsoft.Json.13.0.1\lib\net45\Newtonsoft.Json.dll</HintPath><!-- After --><HintPath>..\packages\Newtonsoft.Json.13.0.3\lib\net45\Newtonsoft.Json.dll</HintPath>
⚠️ Important: The lib\{tfm}\ subfolder in the HintPath depends on which TFM the package ships for. After restore, check the actual folder name. Common patterns:
lib\net45\ — works for net45 through net481
lib\net472\ — specific to net472+
lib\net48\ — specific to net48+
lib\netstandard2.0\ — .NET Standard (works on .NET Framework 4.6.1+)
Restore packages: Run msbuild {SolutionPath/ProjectPath} /t:Restore. If MSBuild restore is unavailable for a packages.config solution, use nuget restore as a fallback.
Verify HintPath: After restore, confirm the DLL exists at the expected path. If the package ships different TFM folders for the new version, update the HintPath accordingly.
Build: Run msbuild {SolutionPath/ProjectPath} /t:Build to verify the project compiles.
Run msbuild {SolutionPath/ProjectPath} /t:Restore. If MSBuild restore is unavailable for a packages.config solution, use nuget restore as a fallback.
Removing a Package
Remove the <package> entry from packages.config.
Remove the corresponding <Reference> from the csproj.
Remove any using directives for the package's namespaces if no longer needed.
Workflow: PackageReference in Old-Style csproj
Some old-style projects use <PackageReference> instead of packages.config. This is less common but valid.
Updating a Package Version
Edit the Version attribute directly in the csproj:
<!-- Before --><PackageReferenceInclude="Newtonsoft.Json"Version="13.0.1" /><!-- After --><PackageReferenceInclude="Newtonsoft.Json"Version="13.0.3" />
Then run msbuild {SolutionPath/ProjectPath} /t:Restore so restore uses MSBuild for old-style projects.
Adding a New Package
Add a <PackageReference> element to an <ItemGroup>:
⚠️ Do NOT use dotnet add package — it may attempt to convert the project to SDK-style format or produce incorrect XML for old-style projects.
Removing a Package
Remove the <PackageReference> element from the csproj.
Key Differences from SDK-Style Package Management
Feature
Legacy (this skill)
SDK-Style (managing-package-references)
Package file
packages.config
None (inline in csproj)
Version location
packages.config + HintPath
<PackageReference Version="...">
Central Package Management
Not supported
Supported via Directory.Packages.props
dotnet add package
Do NOT use
Recommended
Assembly references
Explicit <Reference> with HintPath
Automatic
Restore command
msbuild /t:Restore (nuget restore fallback for packages.config when needed)
dotnet restore
Package folder
packages/ at solution root
Global cache (~/.nuget/packages/)
Common Issues
HintPath version mismatch after package update
Symptom: Build error — assembly not found.
Cause: packages.config version was updated but <HintPath> in csproj still points to old version.
Fix: Update the version number in the HintPath to match the new package version.
Package not compatible with target framework
Symptom: NuGet restore warning about package not supporting target framework.
Cause: Package doesn't have a compatible TFM folder.
Fix: Find a compatible version of the package, or check if a newer version supports net481.
Mixed package management in solution
Symptom: Some projects use packages.config, others use PackageReference.
Cause: Projects were created at different times or partially migrated.
Fix: Handle each project according to its format. Do NOT convert between formats during a Framework version upgrade.
