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!

    Visual Studio Extensions

    Scheduled Pinned Locked Moved Support
    proget
    4 Posts 2 Posters 10 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.
    • M Offline
      mark.barnard_0845
      last edited by

      I can see Visual Studio Extensions are in your roadmap. I was wondering if you can give any timescales on this? We are having to support these manually in IIS but we use ProGet quite extensively so would be great if we could use this also.

      Product: ProGet
      Version: 4.6.7

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

        We're actually planning it in the next release (4.7) for a partnership (to be announced soon). It may come in a maintence release as a preview, depending on the 4.7 schedule.

        That said... unfortunately, unlike NuGet, the "VS marketplace" uses a completely different and undocumented API (which means there is no "connector" possibility)... and you can't replace the built-in gallery anyway (Visual Studio limitation). So, it's not nearly as useful, which is why we've held off on it for a bit.

        1 Reply Last reply Reply Quote 0
        • M Offline
          mark.barnard_0845
          last edited by

          Interesting, thanks for the info. It’s not completely clear to me what the new functionality will involve. You seem to be referring to a server-side “pass-through” connector that connects to the public galleries, but this is not what we’re interested in. We want ProGet to simply host our own extensions in a way that VS recognises. The API that VS uses to talk to a gallery is standard and documented, as it’s just an atom feed ( https://en.wikipedia.org/wiki/Atom_(standard) ). Having an API to upload new extensions would be a bonus, so that we could get TeamCity “publish” jobs to update them, as we do for nuget packages.

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

            Yes, that's precisely what it would be; an ATOM feed for private galleries that you can push extensions to. I think only MyGet supports it now, so we will look to them for how they handle pushing, so it can be consistent.

            Most of our enterprise customers wanted to create a workflow like they do with NuGet.org, with only certan public packages in the feed, etc. THat is, they didn't have custom extensions, they only wanted to restrict or cache public extensions for their developers.

            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