1. In your extension solution, update theVSSDK Build Tools package to the latest version via NuGet Package Manager.
2. In your VSIX manifest, add aProductArchitecture tag specifyingarm64 and make sure yourPrerequisites tag includes VS 2022.

   

    

3. Under your project’sProperties>Build, set your build target toAnyCPU (orArm64if you want an Arm64-exclusive extension).

   

    

   

    

For more details on making your extension arm64-compatible (especially for native extensions), check out theupdated documentation on migrating extensions.

Upload your new extension versions on a single Marketplace entry

Once you’ve updated your extension in VS, it’s time to publish your Arm64 extension to the Marketplace!  We 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.

In the browser-based Marketplace, you have the option to download the extension payload that’s right for your CPU architecture.  In Visual Studio’s Extension Manager, you will only see extensions compatible for VS instance.

How to submit Visual Studio 2022 AMD64 and Arm64 extension payloads?

The extension upload and publishing remains unchanged, whether you have already published a Visual Studio 2022 extension or want to publish a new extension.  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.  If you’re an extension user, this will help you find the right extension for their needs.  To upload your Arm64 extension to an existing extension entry:

1. Go to theManage Publishers & Extensions page and click onEdit.

   

2. Upload the new payload. Make sure the new payload has same extension identifier, version, and different target platform.
3. Click onUpload andSave.

Once the payload is validated and is scanned for viruses, you’ll notice that the extension’s entry page now offers multiple download options.

What’s next for Arm64 extensions?

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.

If you’re an extender, please share your feedback on the Arm64 migration experience and if you’re an extension user, be on the lookout for your favorite extensions in Arm64 Visual Studio!