Rules to Better Nuget

Since 1990, SSW has supported the developer community by publishing all our best practices and rules for everyone to see.

If you still need help, go to SSW Consulting Services and book in a consultant.

Show me

#1
Do not avoid checking in nuget or npm packages into source control?
Reasons for avoiding checking Nuget or Npm packages
1. Distributed version control systems, such as Git, include full copies of every version of every file within the repository. Binary files that are frequently updated lead to significant bloat and lengthens the time it takes to clone the repository.
2. When packages are included in the repository, developers are liable to add references directly to package contents on disk rather than referencing packages through NuGet, which can lead to hard-coded path names in the project.
#2
Do you create a private repository for reusable internal code?
Nuget is great for managing publicly available packages, but it’s also surprisingly easy to create and publish your own packages to your own nuget server for internal code reuse across multiple solutions.
#3
Do you know the best NuGet Packages?
The best NuGet packages are:
#4
Do you update your packages regularly?
NuGet makes it easy to find and apply package updates – but this still must be performed manually.

per page

1 - 4 of 4 items

per page

1 - 4 of 4 items