NuGet Reviews

What sets NuGet apart is its robust handling of complex package dependencies, simplifying version control and reducing the risk of conflicts when integrating new components. For custom packages, it allows us to maintain secure, credential-protected private repositories. Combined with our automated CI/CD pipelines, NuGet enables seamless internal package distribution.

One limitation we've encountered is its sensitivity to network stability during downloads. Even brief connectivity issues can trigger errors that are not always easy to trace or resolve.

NuGet has proven to be a reliable tool for managing libraries and reusable components in a structured way. Its integration with Visual Studio offers a clean and intuitive graphical interface, which lowers the learning curve and encourages cross-team collaboration. It has also supported the maintenance of a well-organized internal repository, with clear version tracking, change logs, and access control.

We can search any libraries that we need and update was more easy then any others packages systems

It should automatically detect what version we are using and what we should install

As a .Net developer, All the time I am using for my daily work in the office or at home. Best open source libraries collection in .

Easy to use. Either utilizing IDE tooling or as a stand alone command line tool. Integrated into the majority of developments and devops tools chains. It provides painless and seamless integrations of 3rd party libraries and tooling to your applications without much technical knowledge.

End quality is dependent on the actual package developer. Sometimes circular chain dependencies can be created forcing work around inside the software. Command line tooling can take some work to get used to and the package viewer software is lacking features.

No more tracking down dozens of dependencies or committing 3rd part code to your repositories. Nuget alleviates most of the difficulties in consuming 3rd party libraries in you custom solutions. In the past resolving deep dependably trees in 3rd party libraries was a nightmare but Nuget has made it a practical part of an effective software development life cycle.

It's the best way to manage the dlls and any other project dependencies

No dislikes as such, It can be more easy

Automation Framework Packages, Internal Microservices Packages 4.

.Easy UI

Also simple console command

Good search

Update options also good

Best way to write test scripts.

Nuget is the best way tp write tests and upload

data driven test needs to be enhanced for nugrt

Test app written and uploading test

- Helps sharing .Net libraries across the teams and projects.

- Backward compatibility.

- Sometimes failed to upload the new package using nuget CLI.

- Sharing common libraries that used by different teams and different projects.

For me, NuGet's best feature is it's package gallery which I use to publish my own libraries.

Unfortunately library authors do not always update their project's NuGet instance promptly, resulting in downloading an older version of the library.

Try to download a package with the fewest dependencies which meets your needs, if possible.

NuGet helps solve easily and effortlessly the issue of library dependencies, and also provides more visibility for my own developed packages.

The two most helpful things are,

you can always create a NuGet repository locally and manage your dll(s)

you can layout automated build pipelines(CI/CD) without thinking about your assemblies. It automatically resolve all dependency from package.config file in the project build on Microsoft technology.

No such dislikes yet. Without a proper knowledge you can never play around with NuGet.

After 10 years of working with .NET code, when I started using Nuget I thought, why? Why should I use an slow tool that sometimes fail when I can reference directl my dlls. The reason is automation, version managing among projects, auto-deploy of versions on cloud environments...

NuGet sometimes is super slow when updating packages and forces some kind of folder structures.

If you use external .NET libraries, use Nuget PLEASE

Referencing external libraries and managing different versions of them among projects. Managing libraries and versions easily in .