Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Continuous growing of package body
-
We started using ProGet to host our packages. With our project still being in the early development phase we push packages often to our server. Our team is very distributed over the world so the pulling of packages to local computer is very important. We have noticed when we do a Nuget.exe -Update on a project and it pulls down the package from the server, it downloads the complete version xml list. On average that XML file is already between 300-550kb per package and growing by the day. Now we've been on ProGet for about 6 weeks, and with this growing in version XML file size it is going to be a real problem .
I have noticed that when we run the update that the "Microsoft*" packages all of them the "body length" in Fiddler is all around 461 bytes, and the body only contain one version.
Our package in the other hand the body in Fiddler contains all the versions from day one.
Are we using ProGet wrong, or maybe a setting somewhere?Product: ProGet
Version: 3.1.0 -
At some point, the NuGet client started requesting every package version instead of just the latest for updates. The only way to fix this on our end is to add paging/result limiting for feed output. We could hack in a configurable result limit pretty easily which should fix this for you in a maintenance release.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login