{"id":225676,"date":"2019-06-11T08:00:17","date_gmt":"2019-06-11T15:00:17","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=225676"},"modified":"2019-06-10T09:13:52","modified_gmt":"2019-06-10T16:13:52","slug":"create-a-private-gallery-for-self-hosted-visual-studio-extensions","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/create-a-private-gallery-for-self-hosted-visual-studio-extensions\/","title":{"rendered":"Create a private gallery for self-hosted Visual Studio extensions"},"content":{"rendered":"

Most Visual Studio extension authors publish their extensions to the public Marketplace to allow everyone to install them and benefit from the large and open ecosystem. However, some companies create extensions for internal use only. A private gallery allows them to distribute the extensions easily with the same auto-update capabilities enjoyed by any public Marketplace extension. And now, we’ve streamlined the process even more so that you can easily create a private gallery for your team or organization.<\/p>\n

\"\"<\/p>\n

Visual Studio 2010 introduced support for private galleries, but few used them due to lacking samples and tooling. A lot has changed since then and the private gallery support has seen several updates to support extension packs and other more recent features.<\/p>\n

The anatomy of a private gallery<\/h2>\n

A private gallery is an ATOM feed XML File<\/a> that contains meta data about the extensions. Registering the gallery with Visual Studio can be done either by the user manually under Tools -> Options<\/strong> or by an extension using a custom .pkgdef file (example<\/a>).<\/p>\n

\"\"<\/p>\n

The ATOM feed can be located on a web server, file system or file share. After registering the gallery, a new category appears under the Online<\/em> tab in the Extension Manager dialog as shown in the first screenshot above.<\/p>\n

Create the ATOM feed<\/h2>\n

The open source tool Private Gallery Creator<\/a> makes it straightforward to create the ATOM feed. Download the executable and run it in a folder containing the VSIX files you wish to include in the feed. The tool analyzes the VSIX files and extracts the metadata needed to produce a file called feed.xml in the same folder.<\/p>\n

You could also set up a CI\/CD pipeline that automatically executes the tool to update the feed. In addition, the tool has a \u201cwatch\u201d feature to automatically produce a new feed any time a VSIX file is added or modified in the same folder.<\/p>\n

Set it up in only four steps<\/h2>\n

Here\u2019s a recap of how to set up a private gallery:<\/p>\n

    \n
  1. Put your .vsix files into an empty folder accessible to all consumers of the gallery<\/li>\n
  2. Download PrivateGalleryCreator.exe<\/a> executable into the same folder<\/li>\n
  3. Double-click PrivateGalleryCreator.exe to produce the feed.xml file<\/li>\n
  4. Register the feed in Visual Studio manually or from an extension\u2019s .pkgdef file<\/li>\n<\/ol>\n

    In summary<\/h2>\n

    You can learn more about private galleries from the documentation<\/a> and by checking the Private Gallery Creator project on GitHub<\/a>. There are a few public offerings for hosted private galleries such as MyGet<\/a> and Open VSIX Gallery<\/a> that may be worth looking into as well.<\/p>\n

    We\u2019d love to hear about how you use private galleries today or why you don\u2019t use them, so please sound off in the comments below.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Most Visual Studio extension authors publish their extensions to the public Marketplace to allow everyone to install them and benefit from the large and open ecosystem. However, some companies create extensions for internal use only. A private gallery allows them to distribute these extensions with ease.<\/p>\n","protected":false},"author":642,"featured_media":225679,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1388,155],"tags":[294,12],"class_list":["post-225676","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-extensibility","category-visual-studio","tag-extensions","tag-visual-studio"],"acf":[],"blog_post_summary":"

    Most Visual Studio extension authors publish their extensions to the public Marketplace to allow everyone to install them and benefit from the large and open ecosystem. However, some companies create extensions for internal use only. A private gallery allows them to distribute these extensions with ease.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/225676","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/642"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=225676"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/225676\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/225679"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=225676"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=225676"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=225676"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}