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!

    Pushing VSIX Packages

    Scheduled Pinned Locked Moved Support
    continuous-integrationprogetvisual-studio
    7 Posts 1 Posters 25 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

      I successfully upgraded to ProGet 4.7.2 and set up a VSIX feed. I managed to manually upload a VSIX package, but I'd like to know if there is a way to automate or script the package upload.

      Thanks,
      Jon

      Product: ProGet
      Version: 4.7.2

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

        It's a bug that this isn't documented, but you can PUT or POST a .vsix file to:

        http://<proget>/vsix/<FeedName>
        
        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          Hi Dean, thank you for the quick response.

          I tried posting the binary vsix file using the curl command-line client like this:

          curl -D- -u Admin:Admin -X POST --data-binary @TsdLib.StarterKit.vsix http://proget:81/vsix/TSD_Vsix_Experimental

          And I get this response:

          HTTP/1.1 400 Bad Request Cache-Control: private Content-Length: 23 Content-Type: text/plain; charset=utf-8 Server: Microsoft-HTTPAPI/2.0 X-AspNet-Version: 4.0.30319 X-UA-Compatible: IE=edge X-ProGet-Version: 4.7.1.4 Date: Tue, 21 Feb 2017 21:35:27 GMT

          Invalid version number.

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

            Appears to be another bug. Probably why this hasn't been documented yet :)

            You may be able to work around by adding a name+version to the url, such as:

            http://proget:81/vsix/TSD_Vsix_Experimental/rubbish/1.0.0
            

            It shouldn't even matter what you use, it could literally be the values in that example, as long as there's a name and version number. In any case, we'll have a fix in v4.7.3.

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

              Hi Dean, I tried adding the /rubbish/1.0.0 to the end of the url but now I get a the 404 response code, with Unknown API endpoint message.

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

                This is now fixed in v4.7.3.

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

                  Thanks Dean, upgrading to 4.7.3 has solved the issue!

                  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