NuGet
NuGet
NuGet
Overview
What is NuGet?
NuGet is the package manager for .NET. The NuGet client tools provide the ability to produce and consume packages. The NuGet Gallery is the central package repository used by all package authors and consumers.
Read moreRecent Reviews
Reviewer Pros & Cons
View all pros & consPricing
View all pricingEntry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Would you like us to let the vendor know that you want pricing?
3 people want pricing too
Alternatives Pricing
Product Details
- About
- Tech Details
What is NuGet?
NuGet is the package manager for .NET. The NuGet client tools provide the ability to produce and consume packages. The NuGet Gallery is the central package repository used by all package authors and consumers.
NuGet Technical Details
Operating Systems | Unspecified |
---|---|
Mobile Application | No |
Comparisons
View all alternativesCompare with
Reviews and Ratings
 (3)
Reviews
(1-2 of 2)- Popular Filters
Companies can't remove reviews or game the system. Here's why
NuGet helps to create packages that can be shared over the public and private networks. The package mainly contains useful code in the form of dlls and the other necessary files required. The consumer of packages is mainly .Net projects. With the help of a visual studio, it can be easily downloaded and used.
- Maintains package repository very well
- Integration with the Visual Studio editor
- Easy upload and downloads
- Incomplete download resume in case of network disruptions
- Adding user friendly platform to add and update the packages
- Package creation option in Visual Studio
- Publish useful packages
- Share the published packages across different projects
- Using existing publicly available free packages
- Saves a rework by sharing the common functionalities across the projects
- Helped to optimize the given package using a central repository
- Helped to make use of existing useful packages
Didn't use another package manager as NuGet was our favorite since the beginning.
April 25, 2022
NuGet - Welcome to .NET world
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!
- Apache Maven and Gradle
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.