C# 7.1 and .NET Core 2.0 - Modern Cross-Platform Development - Third Edition
by Mark J. Price, Dustin Heffron, Efraim Kyriakidis
Fixing dependencies
To consistently restore packages and write reliable code, it's important that you fix your dependencies. Fixing dependencies means you are using the same family of packages released for a specific version of .NET Core, for example, 1.0.
To fix dependencies, every package should have a single version with no additional qualifiers. Additional qualifiers include release candidates (rc4) and wildcards (*). Wildcards allow future versions to be automatically referenced and used because they always represent the most recent release. But wildcards are therefore dangerous, because it could result in the restoration of future incompatible packages that break your code.
The following dependencies are NOT fixed and should be avoided: ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access