{"id":239478,"date":"2022-09-22T09:00:23","date_gmt":"2022-09-22T16:00:23","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=239478"},"modified":"2022-09-23T10:17:31","modified_gmt":"2022-09-23T17:17:31","slug":"now-introducing-arm64-support-for-vs-extensions","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/now-introducing-arm64-support-for-vs-extensions\/","title":{"rendered":"Now Introducing Arm64 Support for VS Extensions!"},"content":{"rendered":"

Back in June, we announced Arm64 Visual Studio 2022 application, the first version of Visual Studio that natively supports building and debugging Arm64 apps on Arm-based processors.\u00a0 Now, we\u2019re excited to announce the extensions you write, and use, are supported in Arm64 VS!<\/p>\n

 <\/p>\n

Adding Arm64 support to your new or existing extension<\/h3>\n

Making your extension Arm64-compatible can be accomplished in three easy steps:<\/p>\n

    \n
  1. In your extension solution, update the VSSDK Build Tools package<\/a> to the latest version via NuGet Package Manager.<\/li>\n
  2. In your VSIX manifest, add a ProductArchitecture<\/strong> tag specifying arm64<\/strong> and make sure your Prerequisites<\/strong> tag includes VS 2022.\n

    \"ProductArchitecture<\/a>
    ProductArchitecture Tag for Arm64<\/figcaption><\/figure><\/p>\n

     <\/li>\n

  3. Under your project\u2019s Properties<\/strong> ><\/strong> Build<\/strong>, set your build target to AnyCPU<\/strong> (or Arm64 <\/strong>if you want an Arm64-exclusive extension).\n

    \"Arm64<\/a>
    Arm64 Build Property Settings<\/figcaption><\/figure><\/p>\n

     <\/p>\n

    \"Arm64<\/a>
    VSIX Manifest with an Arm64 Installation Target<\/figcaption><\/figure><\/p>\n

     <\/li>\n<\/ol>\n

    For more details on making your extension arm64-compatible (especially for native extensions), check out the updated documentation on migrating extensions<\/a>.<\/p>\n

     <\/p>\n

    Upload your new extension versions on a single Marketplace entry<\/h3>\n

    Once you\u2019ve updated your extension in VS, it\u2019s time to publish your Arm64 extension to the Marketplace! \u00a0We are happy to announce that as an extension author, now you can publish your Arm64 extension alongside the amd64 (64-bit) version of your extension on a single Marketplace entry.<\/p>\n

    \"Arm64<\/a>
    Example of a single-Page consolidation for Arm64 extension version<\/figcaption><\/figure><\/p>\n

     <\/p>\n

    In the browser-based Marketplace, you have the option to download the extension payload that\u2019s right for your CPU architecture.\u00a0 In Visual Studio\u2019s Extension Manager, you will only see extensions compatible for VS instance.<\/p>\n

     <\/p>\n

    How to submit Visual Studio 2022 AMD64 and Arm64 extension payloads?<\/h3>\n

    The extension upload and publishing remains unchanged, whether you have already published a Visual Studio 2022 extension or want to publish a new extension.\u00a0 Having a single entry for multiple payloads will help extension authors to reduce the number of extensions they have to maintain for each Visual Studio version.\u00a0 If you\u2019re an extension user, this will help you find the right extension for their needs.\u00a0 To upload your Arm64 extension to an existing extension entry:<\/p>\n

      \n
    1. Go to the Manage Publishers & Extensions<\/strong> page and click on Edit<\/strong>.\n

      \"Manage<\/a>
      Manage Marketplace Extensions page<\/figcaption><\/figure><\/li>\n
    2. Upload the new payload. Make sure the new payload has same extension identifier, version, and different target platform.<\/li>\n
    3. Click on Upload<\/strong> and Save<\/strong>.<\/li>\n<\/ol>\n

      Once the payload is validated and is scanned for viruses, you\u2019ll notice that the extension\u2019s entry page now offers multiple download options.<\/p>\n

       <\/p>\n

      What\u2019s next for Arm64 extensions?<\/h3>\n

      As part of the extension consolidation effort, we want to enable extension authors to merge their separate, existing extension listings for different VS versions into a single listing, which will further improve extension discoverability.<\/p>\n

      If you\u2019re an extender, please share your feedback on the Arm64 migration experience and if you\u2019re an extension user, be on the lookout for your favorite extensions in Arm64 Visual Studio!<\/p>\n

       <\/p>\n","protected":false},"excerpt":{"rendered":"

      Back in June, we announced Arm64 Visual Studio 2022 application, the first version of Visual Studio that natively supports building and debugging Arm64 apps on Arm-based processors.\u00a0 Now, we\u2019re excited to announce the extensions you write, and use, are supported in Arm64 VS!   Adding Arm64 support to your new or existing extension Making your […]<\/p>\n","protected":false},"author":651,"featured_media":255385,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1388,155],"tags":[294,12,6815],"class_list":["post-239478","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-extensibility","category-visual-studio","tag-extensions","tag-visual-studio","tag-visual-studio-2022"],"acf":[],"blog_post_summary":"

      Back in June, we announced Arm64 Visual Studio 2022 application, the first version of Visual Studio that natively supports building and debugging Arm64 apps on Arm-based processors.\u00a0 Now, we\u2019re excited to announce the extensions you write, and use, are supported in Arm64 VS!   Adding Arm64 support to your new or existing extension Making your […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/239478","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\/651"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=239478"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/239478\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/255385"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=239478"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=239478"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=239478"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}