Hide Transitive NuGet Dependencies with PrivateAssets
Learn how to hide a transitive NuGet package from consumers using the PrivateAssets attribute in PackageReference.
Loading…
ReadMeFeed / Community knowledge
#package-reference
Real questions. Useful conversations. Find the people who know your stack.
dotnet
nugetNuGet Central Package Management vs Per‑Project PackageReference: A Decision Guide
Decide whether to adopt NuGet Central Package Management (CPM) or keep per‑project PackageReference. Compare constraints, trade‑offs, and see a step‑by‑step migration example with Directory.Packages.props.
PackageReference upgrade with lock file: reverting to prior dependency graph after failed resolution
A design question concerns returning a SDK-style project using PackageReference to a known good dependency graph when a version change leads to unresolvable or undesired transitive resolution. PackageReference stores dependency versions in the project file and NuGet resolves the transitive graph during restore, writing project.assets.json and optionally pack
Lock-file deterministic restore vs explicit version downgrade for NuGet rollback reproducibility
Goal is safe recovery from a breaking NuGet upgrade in an SDK-style project using PackageReference, with reproducibility across developer machines and CI. Two documented approaches exist. Lock-file deterministic restore relies on a committed packages.lock.json and locked-mode restore to detect any change to the resolved graph before build. Explicit version d