Compare NuGet and ProGet 
- Users report that ProGet excels in package access control with a score of 8.8, allowing for granular permissions and security settings, while NuGet, although functional, does not provide the same level of detailed access management.
- Reviewers mention that ProGet's package tracking feature, rated at 9.0, offers comprehensive visibility into package versions and dependencies, which is a significant advantage over NuGet's tracking capabilities.
- G2 users highlight that ProGet's automation features, scoring 7.7, streamline workflows effectively, whereas users on G2 note that NuGet's automation is less robust, leading to more manual processes.
- Users say that ProGet's rollback functionality, rated at 8.6, is particularly praised for its ease of use, allowing teams to revert to previous package versions quickly, while NuGet's rollback options are seen as more cumbersome.
- Reviewers mention that ProGet's integration capabilities, scoring 8.2, are well-regarded for connecting with various CI/CD tools, whereas NuGet's integration options are perceived as limited by some users.
- Users report that ProGet's vulnerability checks, with a score of 6.4, are a critical feature for maintaining security, but they feel that NuGet's checks are less comprehensive, leading to potential risks in package management.
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...
I have nothing to complain about regarding that.
What I like best is the manage your own internal libraries / packages. The system can be setup quickly and the interface is easy to navigate. Easy to manage multiple version of your packages when you are developing internal libraries that are used inside...
Only available for windows, and sometimes is very slow, and hard to understand the log error.
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...
What I like best is the manage your own internal libraries / packages. The system can be setup quickly and the interface is easy to navigate. Easy to manage multiple version of your packages when you are developing internal libraries that are used inside...
I have nothing to complain about regarding that.
Only available for windows, and sometimes is very slow, and hard to understand the log error.
