or Microsoft., and have version numbers between 4.0.0 and 4.3.1. The problematic packages generally start with System. NET Core 3.0 or higher project, and a RuntimeIdentifier is specified. NET Core 1.0 and 1.1 are not compatible with each other when they are referenced together in a. Project -> System.IO.FileSystem 4.0.1 -> System.IO.FileSystem.Primitives (>= 4.0.1) IssueĬertain combinations of packages which shipped with. Project -> System.IO.FileSystem 4.0.1 -> .FileSystem 4.3.0 -> System.IO.FileSystem.Primitives (>= 4.3.0) Reference the package directly from the project to select a different version. In the example above, you would change the package reference to PackageC 2.0.0:ĭetected package downgrade: System.IO.FileSystem.Primitives from 4.3.0 to 4.0.1. The author of PackageA has explicitly downgraded to PackageC 1.1.0 from PackageC 2.0.0. That is because of the direct-dependency-wins rule - when resolving packages, NuGet tries to honor the intent of the package author. 'Project' -> 'PackageA' 1.0.0 -> 'PackageC' (>= 1.1.0) IssueĪ dependency package specified a version constraint on a higher version of a package than restore ultimately resolved. In the example above, you would change the package reference to PackageB 4.0.0:Įxample 2 Detected package downgrade: 'PackageC' from 2.0.0 to 1.1.0. To the project exhibiting the restore warning, add a package reference to the higher version of the package. That is because of the direct-dependency-wins rule - when resolving packages, the direct package version in the subgraph will override that of the distant packages with the same ID. 'Project' -> 'PackageA' 4.0.0 -> 'PackageB' (>= 4.0.0)Ī dependency package specified a version constraint on a higher version of a package than restore ultimately resolved.
In this article Example 1 Detected package downgrade: 'PackageB' from 4.0.0 to 3.5.0.
0 kommentar(er)
