JFrog Artifactory vs. NuGet

It works at scale and a large number of accessible pipelines for searching, repository updates and indexing will become easier. JFrog provides end-to-end solutions for all DevOps needs. With this, Jfrog Artifactory specifically implements the management of highly available repositories, with a smooth interface and integration with all the main CI tools on the market.

Incentivized

Whenever your projects need some packages which are available on NuGet it is easy to consume them with the help of tools such as Visual Studio, and MSBuild. We can add customized functionality to existing packages and can host them as a separate packages easily. Packages that depend on other packages are well managed by NuGet.

Incentivized

• Artifactory Management acting as a repository manager of docker images, application and component dependencies
• Automate pipelines and thereby releasing changes faster
• Supports high availability and scalability with multi site replication

Incentivized

• 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

Incentivized

• We can always use support for more different types of packages in Artifactory.
• We also would like to see the Artifactory X-Ray produce continue to mature.

Incentivized

• Incomplete download resume in case of network disruptions
• Adding user friendly platform to add and update the packages
• Package creation option in Visual Studio

Incentivized

The main problem that seems intractable is getting the checksum of the artifact. Managing container artifacts is a game changer for us during project execution, as the container artifact type exposes all base image and Docker file steps. This makes debugging or analysis easier. Jfrog Artifactory provides promotion feature and can automated from one environment repo to another environment repo before the deployment occurs.

Incentivized

Support tickets take days to respond. The most basic of questions that should be knocked out in a few hours don't get answers for days. Tickets are also closed without resolution.

JFrog Artifactory has a much more friendly GUI, making package exploration less of a chore to do. Other than that, their features are pretty much comparable to each other. Both support multiple types of packages; both have API that can integrate well with CI/CD pipelines.

Incentivized

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.

Incentivized

• So many times it happens at the time of dependency resolution some of the servers are down e.g NPM, Maven central, PiPy in that cause our builds starts failing. By proxying these repositories with JFrog this is never happened again.
• It reduced the additional cost of container image registry and management effort.
• Support of integration with Build, Monitoring, and CI tools resulted in smooth automation and management.

Incentivized

• 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

Incentivized