ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #nuget
Learn how Rider’s NuGet tool window streamlines package installation, source configuration, and dependency resolution, with a step‑by‑step example, pitfalls to avoid, and best‑practice tips for .NET developers.
Establish verifiable trust boundaries for NuGet packages using author signatures and repository countersignatures. Covers minimal design, allowlist configuration, pipeline enforcement, and failure-mode mitigations.
Commit the exact NuGet restore graph with packages.lock.json to prevent transitive dependency drift across developers and CI for .NET projects.
Stop guessing why third-party NuGet packages are crashing. Learn how to use Rider's integrated decompiler to read dependency code and step into external methods during debugging.
Step‑by‑step diagnostic guide for resolving NuGet version conflict errors in .NET solutions, with checks, fixes, and verification tips.
Rider centralizes NuGet work with a tool window, dependency graph, and updates view. Learn how to spot transitive conflicts, migrate packages.config to PackageReference, and verify changes without leaving the IDE.
An architecture note on NuGet Central Package Management: when one Directory.Packages.props is the right design, how to make it a trust boundary with source mapping and locked-mode restore, and the signals that say to split it.
Learn how NuGet lock files enable deterministic package restores, see a concrete example with dotnet CLI, and understand the trade‑offs of using locked mode.
Guidance on selecting fixed or floating NuGet versions, using Central Package Management and lock files for reproducible builds.
dotnet