Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    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!

    NuGet $batch update request

    Scheduled Pinned Locked Moved Support
    proget
    11 Posts 1 Posters 17 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      If a NuGet update request query string would exceed the IIS maximum of 2048, NuGet uses a special $batch url to request package details for available updates instead of passing the Ids of all packages in the query string. When this happens, I am getting a 404 error from ProGet and cannot do an update at the solution level and have to do it for each individual project, which is really tedious with 40 projects in the solution :)

      Is the $batch update something that is just not supported in ProGet, or is there some configuration that is required to support this?

      Product: ProGet
      Version: 3.2.1

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        We are currently adding support for this; it should be included in the next maintenance version (v3.2.2) of ProGet (or minor release v3.3 if we happen to release that first).

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          Has this issue been fixed in a subsequent version to 3.2.1?

          Product: ProGet
          Version: 3.2.1

          Thanks, Tim.

          1 Reply Last reply Reply Quote 0
          • ? This user is from outside of this forum
            Guest
            last edited by

            Is there any ETA on when 3.2.2 or 3.3 might be released? This is a pretty big blocker for us right now, and is causing us to look at other solutions.

            1 Reply Last reply Reply Quote 0
            • ? This user is from outside of this forum
              Guest
              last edited by

              This has been fixed and we are using it internally. It is possible the new version will be out today (2014/11/21) barring any unforeseen circumstances. If not, next Monday.

              Beyond that, there are some performance, indexing, and other improvements in this next version.

              1 Reply Last reply Reply Quote 0
              • ? This user is from outside of this forum
                Guest
                last edited by

                That's great news, thanks!

                1 Reply Last reply Reply Quote 0
                • ? This user is from outside of this forum
                  Guest
                  last edited by

                  Just verifying that this has indeed been fixed in 3.3.1. Working great now, thanks :)

                  1 Reply Last reply Reply Quote 0
                  • ? This user is from outside of this forum
                    Guest
                    last edited by

                    Does this still work in 3.4.x, ProGet seems to be having trouble with $batch Verb and POST method?

                    1 Reply Last reply Reply Quote 0
                    • ? This user is from outside of this forum
                      Guest
                      last edited by

                      Yes this seems to have regressed in 3.4.x. It worked when I was using a legacy feed, but once I migrated to the new feed the problem returned.

                      1 Reply Last reply Reply Quote 0
                      • ? This user is from outside of this forum
                        Guest
                        last edited by

                        Yes, it appears that moving some of the API endpoint URLs to fix a different issue involving authentication with the nuget client is causing this.

                        This happened in 3.4.7, this issue:

                        PG-334 - FIX: Move all /api/v2 url endpoints to /nuget
                        

                        We'll fix in the next release.

                        1 Reply Last reply Reply Quote 0
                        • ? This user is from outside of this forum
                          Guest
                          last edited by

                          Just wanted to let everyone know who's affected by this that we have a fix in 3.5.0. It's officially classified as a beta version, but only due to some database schema changes. The release notes and download links are here: http://inedo.com/proget/versions

                          1 Reply Last reply Reply Quote 0

                          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
                          • 1 / 1
                          • First post
                            Last post
                          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation