Hide Transitive NuGet Dependencies with PrivateAssets
Learn how to hide a transitive NuGet package from consumers using the PrivateAssets attribute in PackageReference.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to hide a transitive NuGet package from consumers using the PrivateAssets attribute in PackageReference.
Stop fighting version drift in multi-project .NET solutions. Learn how to use NuGet Central Package Management (CPM) to define all dependency versions in one place.
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.
Declare every NuGet package version once in Directory.Packages.props and let each .csproj reference packages by name only. How CPM works, what transitive pinning buys you, and the mistakes that trigger NU1008 restore errors.
Learn how to diagnose and fix MSBuild project load failures and NuGet restore issues in JetBrains Rider with a step‑by‑step checklist.
A decision guide that compares Directory.Packages.props with per‑project PackageReference versions, outlines constraints, and shows a concrete implementation and verification steps.
Learn how NuGet restore resolves dependencies, generates asset files, and manages the global cache to ensure consistent .NET builds.
Compare pinned, floating, and centrally managed NuGet versions, with a concrete CPM plus lock-file setup and restore-based checks to confirm what actually resolved.
Design a secure, reproducible NuGet restore process using mirrors, trust boundaries, and locked-mode verification to prevent supply chain risks in CI pipelines.