NuGet - Welcome to .NET world
April 25, 2022

NuGet - Welcome to .NET world

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with NuGet

We used NuGet as an artifact/dependency repository for a couple of .NET Framework / .NET Core projects that we worked on. We pointed to some public repositories for common, publicly available packages. And we maintained our own private, credentials-protected repositories for our proprietary packages at the same time. We also made the distinction between "testing" repositories & "production" ones for our private use.
  • The built-in package explorer / manager in Visual Studio work reliably
  • Integration with popular web-based repository manager is good
  • Command-line options are enough even for complex use cases like publishing to private, credentials-protected repositories
  • While Ivy / Maven dependencies could be managed completely in text-based format, it's difficult to do so with NuGet
  • Documents regarding enterprise use cases like pushing from automated pipelines could be improved
  • Managing NuGet dependencies between multiple projects could be a chore
  • Dependency management
  • Storing / publishing built packages
  • Artifact repositories for dev work / automated pipelines
  • For the way we worked, dependency management is something must-have
  • Having a place to reliably store / publish then later retrieve packages helps with setting new dev env & makes automated pipelines possible
  • We deliver built packages to customers straight from our repositories as well!
Not really have a choice here, especially when working with .NET Framework / .NET Core. At least the built-in GUI of NuGet helps beginners get up to speed quickly. However, advanced users would be able to be more productive with Maven / Ivy thanks to the complete text-based format. Basically, people from the Java world are spoiled by a much better dependency management system.

Do you think NuGet delivers good value for the price?


Are you happy with NuGet's feature set?


Did NuGet live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of NuGet go as expected?


Would you buy NuGet again?


If you're working on some .NET Framework / .NET Core projects, there's no other real choice here. NuGet works well, the heavy reliance on built-in GUI makes it friendly & easy-to-learn for new people, especially those who haven't been used to dependency management topics. But for those coming from the Java world, who are already spoiled by text-based Maven / Ivy, then NuGet could be a chore to work on a daily basis.