Is there a benefit to hosting an internal (remote) NuGet feed through an IIS website vs simply using a shared network folder?
The global-packages folder is where NuGet installs any downloaded package. Each package is fully expanded into a subfolder that matches the package identifier and version number. Projects using the PackageReference format always use packages directly from this folder.
NuGet is an open-source package manager designed for the Microsoft development technologies. The NuGet repository support at Cloudsmith is compatible with Chocolatey, so if you're looking to manage packages on Windows, that's our recommended approach.
If shared UNC access is available, then it is definitely the simpler solution to create an internal feed. However, if the feed has a large number of packages, then the performance will be better when using http because of the caching it's able to do. In the UNC case, NuGet needs to crack open the packages on every operation.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With