-
Notifications
You must be signed in to change notification settings - Fork 250
Restore errors and warnings
This document contains a list of all warnings and errors that may occur during restore.
Generic error from NuGet.
Generic warning from NuGet.
The project does not contain one or more frameworks.
The project does not contain a TargetFramework or TargetFrameworks property.
The project projA does not specify any target frameworks in c:\tmp\projA.csproj.
Invalid combination of inputs along with a CLEAR keyword.
CLEAR may not be combined with other inputs.
'CLEAR' cannot be used in conjunction with other values.
PackageTargetFallback and AssetTargetFallback provide different behavior for selecting assets and can not be used together.
Both PackageTargetFallback and AssetTargetFallback exist in the project.
PackageTargetFallback and AssetTargetFallback cannot be used together. Remove PackageTargetFallback(deprecated) references from the project environment.
A dependency group not be resolved. This is a generic issue for types that are not packages or projects.
The project contains a dependency on an item that does not exist.
Unable to resolve System.Missing for net45
The package id cannot be found on any sources.
The correct package source is missing or the package id has a typo.
Unable to find package System.Missing. No packages exist with this id in source(s): dotnet-core, dotnet-roslyn, NuGet.org
The package id is found but a version within the specified dependency range cannot be found on any of the sources.
The correct package source is missing or the dependency range is incorrect. The range might be specified by a package and not the user.
The user may need to switch to an available version if this package is referenced by the project directly.
Unable to find package NuGet.Versioning with version (>= 9.0.1)
- Found 30 version(s) in NuGet.org [ Nearest version: 4.0.0 ]
- Found 10 version(s) in dotnet-buildtools [ Nearest version: 4.0.0-rc-2129 ]
- Found 9 version(s) in NuGetVolatile [ Nearest version: 3.0.0-beta-00032 ]
- Found 0 version(s) in dotnet-core
- Found 0 version(s) in dotnet-roslyn
No stable versions were found in the dependency range. Pre-release versions were found but are not allowed.
The project specified a stable version for the dependency range. Users need to change this to include pre-release versions.
Unable to find a stable package NuGet.Versioning with version (>= 3.0.0)
- Found 10 version(s) in dotnet-buildtools [ Nearest version: 4.0.0-rc-2129 ]
- Found 9 version(s) in NuGetVolatile [ Nearest version: 3.0.0-beta-00032 ]
- Found 0 version(s) in dotnet-core
- Found 0 version(s) in dotnet-roslyn
A ProjectReference points to a file that does not exist.
The project file is missing from disk or the reference is incorrect.
Project reference does not exist 'c:\a.csproj'. Check that the project reference is valid and that the project file exists.
The project file exists but no restore information was provided for it.
In Visual Studio this could mean that the project is unloaded. From the command line this could mean that the file is corrupt or that it does not contain the custom after imports target needed for restore to read the project.
Unable to read project information for 'c:\a.csproj'. The project file may be invalid or missing targets required for restore.
Dependency constraints cannot be resolved.
Packages contain dependency on exact versions of a package instead of open ended ranges.
Unable to satisfy conflicting requests for {id}: {conflict path} Framework: {target graph}
Unable to resolve dependency constraints between packages.
Packages with dependency constraints on exact versions do not allow other packages to increase the version if needed.
Version conflict detected for NuGet.Versioning. Reference the package directly from the project to resolve this issue.
NuGet.Packaging 3.5.0 -> NuGet.Versioning (= 3.5.0)
NuGet.Configuration 4.0.0 -> NuGet.Versioning (= 4.0.0)
A circular dependency was detected.
A package is authored incorrectly.
Cycle detected: A -> B -> A
A dependency project does not contain a framework compatible with the current project.
The project's target framework is a higher version than the consuming project.
Project ServerWeb is not compatible with netstandard1.3 (.NETStandard,Version=v1.3). Project ServerWeb supports:
- netstandard1.6 (.NETStandard,Version=v1.6)
- netcoreapp1.0 (.NETCoreApp,Version=v1.0)
A dependency package does not contain any assets compatible with the project.
The package does not support the project's target framework.
Package System.ComponentModel.EventBasedAsync 4.0.11 is not compatible with netstandard1.3 (.NETStandard,Version=v1.3). Package System.ComponentModel.EventBasedAsync 4.0.11 supports:
- monoandroid10 (MonoAndroid,Version=v1.0)
- monotouch10 (MonoTouch,Version=v1.0)
- net45 (.NETFramework,Version=v4.5)
- netcore50 (.NETCore,Version=v5.0)
- netstandard1.0 (.NETStandard,Version=v1.0)
- portable-net45+win8+wp8+wpa81 (.NETPortable,Version=v0.0,Profile=Profile259)
- win8 (Windows,Version=v8.0)
- wp8 (WindowsPhone,Version=v8.0)
- wpa81 (WindowsPhoneApp,Version=v8.1)
- xamarinios10 (Xamarin.iOS,Version=v1.0)
- xamarinmac20 (Xamarin.Mac,Version=v2.0)
- xamarintvos10 (Xamarin.TVOS,Version=v1.0)
- xamarinwatchos10 (Xamarin.WatchOS,Version=v1.0)
The package does not support the project's RuntimeIdentifier.
The package does not support the current RuntimeIdentifier. Change the RuntimeIdentifiers used in the project if needed.
System.Example 1.0.0 provides a compile-time reference assembly for a.dll on net461, but there is no compatible run-time assembly.
The package requires features or frameworks not currently supported by the installed version of NuGet.
Upgrade NuGet to fix the issue.
The 'NuGet.Versioning' package requires NuGet client version '5.0.0' or above, but the current NuGet version is '4.3.0'. To upgrade NuGet, please go to http://docs.nuget.org/consume/installing-nuget.
The project restore is attempting to operate on was not found.
The project is missing.
The folder 'c:\projects\a' does not contain a project to restore.
RuntimeSupports contains an invalid profile.
The supports profile was not found in a runtime.json file from the current dependency packages.
Unknown Compatibility Profile: aaa
A dependency project does not import NuGet's restore targets. This is similar to NU1105 but here the project is skipped and ignored instead of causing all of restore to fail. In complex solutions there are often other types of projects that may not support restore.
This can happen for projects that do not import common props/targets which automatically import restore. If the project does not need to be restored this can be ignored.
Skipping restore for project 'c:\a.csproj'. The project file may be invalid or missing targets required for restore.
A direct project dependency was bumped to a higher version than the project specified.
Another dependency package required a higher version and bumped the package up.
Dependency specified was NuGet.Versioning (>= 3.5.0) but ended up with NuGet.Versioning 4.0.0.
A package dependency is missing a lower bound. This does not allow restore to find the best match. Each restore will float downwards trying to find a lower version that can be used. This means that restore goes online to check all sources each time instead of using the packages that already exist in the user package folder.
This is usually a package authoring error.
NuGet.Packaging 4.0.0 does not provide an inclusive lower bound for dependency NuGet.Versioning (> 3.5.0). An approximate best match of 3.6.0 was resolved.
A package dependency specified a version that could not be found. A higher version was used instead, which differs from what the package was authored against.
This means that restore did not find the best match. Each restore will float downwards trying to find a lower version that can be used. This means that restore goes online to check all sources each time instead of using the packages that already exist in the user package folder.
The package sources do not contain the expected lower bound version. If the package expected has not been released then this may be a package authoring error.
NuGet.Packaging 4.0.0 depends on NuGet.Versioning (>= 4.0.0) but 4.0.0 was not found. An approximate best match of 5.0.0 was resolved.
A project dependency does not define a lower bound.
This means that restore did not find the best match. Each restore will float downwards trying to find a lower version that can be used. This means that restore goes online to check all sources each time instead of using the packages that already exist in the user package folder.
The project's PackageReference Version attribute should be updated to include a lower bound.
Project dependency NuGet.Versioning (<= 9.0.0) does not contain an inclusive lower bound. Include a lower bound in the dependency version to ensure consistent restore results.
A dependency package specified a version constraint on a higher version of a package than restore ultimately resolved.
Nearest wins when resolving packages. A nearer package in the graph may have overridden a distant package.
Detected package downgrade: NuGet.Versioning from 4.0.0 to 3.5.0. Reference the package directly from the project to select a different version.
NuGet.Packaging 3.5.0 -> NuGet.Versioning 3.5.0
NuGet.Commands 4.0.0 -> NuGet.Configuration 4.0.0 -> NuGet.Versioning 4.0.0
A resolve package is higher than a dependency constraint allows. In some cases this is intentional and the warning can be suppressed.
A package referenced directly by a project will override dependency constraints from other packages.
Detected package version outside of dependency constraint: x 1.0.0 requires y (= 1.0.0) but version y 2.0.0 was resolved.
PackageTargetFallback was used to select assets from a package. This is a warning to let the user know that the assets may not be 100% compatible.
The package does not support the project framework.
Package 'NuGet.Versioning' was restored using 'portable-net45+win8' instead the project target framework 'netstandard1.5'. This package may not be fully compatible with your project.
An error occurred when reading the feed. IgnoreFailedSources was set to true, converting it to a non-fatal warning. This could contain any message and is generic.
The source is invalid.
Check out the proposals in the accepted & proposed folders on the repository, and active PRs for proposals being discussed today.