nuget
NuGet Errors and Warnings
Error and warning codes emitted by the NuGet package manager during package restore, install, and pack operations for .NET projects.
16 codes
· All codes 16 codes
- NU1100 Unable to Resolve Dependency NuGet could not find a version of the package that satisfies the project's constraints and target framework. Check the package name, version range, and whether the package supports your target framework.
- NU1101 Package Not Found The specified package does not exist in any of the configured package sources. Verify the package ID spelling, ensure the relevant NuGet feed is configured, and check whether you need to authenticate to a private feed.
- NU1102 Package Version Range Not Satisfied No version of the package exists within the requested version range. Widen the version constraint, check for pre-release versions with '-pre', or verify the package exists on the configured feeds.
- NU1103 No Stable Version Found Only pre-release versions of the package are available, but the project does not allow pre-release packages. Explicitly request the pre-release version or wait for a stable release.
- NU1105 Unable to Read Project Information NuGet could not load the project file or extract dependency information from it. The project file may be malformed or reference an SDK that is not installed.
- NU1201 Project Not Compatible With Target Framework A referenced project targets a framework that is incompatible with the consuming project's target framework. Align the target frameworks of both projects, or multi-target the referenced project.
- NU1202 Package Not Compatible With Target Framework The package does not support the project's target framework. Find a newer version that adds the required framework target, switch to a compatible alternative, or change the project's target framework.
- NU1401 Package Requires Newer NuGet Client The package specifies a minimum NuGet client version that is higher than the one installed. Update Visual Studio, the .NET SDK, or the standalone NuGet CLI to a newer version.
- NU1500 Dependency Graph Resolution Error NuGet encountered an error while resolving the package dependency graph. This is usually accompanied by a more specific NU1xxx error that describes the root cause.
- NU1503 Skipping Restore for Project Restore was skipped for a project because NuGet could not load its information. This is a warning in multi-project solutions; the affected project will not have its packages restored.
- NU1601 Package Resolved at Higher Version A package dependency was resolved at a higher version than requested because another dependency in the graph requires it. Review the dependency tree and update the version constraint if needed.
- NU1605 Detected Package Downgrade A package was resolved at a lower version than a direct dependency requires. This usually means a top-level package pins an older version. Add a direct PackageReference with the required version to force the higher version.
- NU1701 Package Restored for Different Framework The package was restored using a fallback target framework instead of the project's actual target. The package may not be fully compatible. Suppress the warning only after verifying the package works correctly at runtime.
- NU3028 Package Signature Timestamp Invalid The timestamp on the package's repository signature has expired or failed chain validation. The package may still be usable; configure NuGet's signature validation policy if needed.
- NU5100 Assembly Outside lib Folder When creating a NuGet package, an assembly was found outside the 'lib' folder and will not be added as a reference by consumers. Move the assembly into the appropriate 'lib/<tfm>/' folder.
- NU5128 Target Framework Mismatch in Package Some target frameworks declared in the package's dependencies group do not have corresponding lib or ref folder entries. Add the missing framework folders or remove the corresponding dependencies group entries.