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.
On Friday, May 10th we hosted both internal and external Visual Studio extension authors in the Workshop room in building 18 on the Microsoft Campus in Redmond. It was a full day event with keynotes and sessions for 60 attendees – half of which attended //build earlier that same week, and half who came just for the Extensibility Day.
We’re excited to announce the preview availability of the new Azure IoT Edge Tools Extension (Preview) for Visual Studio 2019. The extension provides a rich set of functionalities to support development of IoT Edge solutions with Visual Studio 2019:
New Azure IoT Edge project targeting different platforms (Linux amd64,
Visual Studio 2019 starts blocking synchronously autoloaded extensions in version 16.1. We’ve seen a tremendous effort of both 1st- and 3rd-party extensions to implement async background load. It’s been truly amazing to see the community of extension authors stepping up to the task.
Visual Studio 2019 version 16.1 Preview 2 is now available with performance and reliability improvements as well as enhancements to C++, debugging, extensibility, and the IDE experience.
Enable custom filters for your project templates with language, platform, and project type tags for increased discoverability in the New Project Dialog. In this walkthrough, you will learn how to build a Visual Studio project template, add tag(s) to it, and deploy it as a Visual Studio extension.
Take advantage of new features for extension authors in Visual Studio 16.1 Preview 1. This includes support for referencing Shared Projects for a VSIX project, per-monitor awareness, a new SDK meta package, and more.
Please join us for a day full of Visual Studio extensibility deep dives, geek-outs, and networking on Friday, May 10th, 2019 at the Microsoft campus in Redmond. Our agenda is intended for existing and new Visual Studio IDE (not VSCode) extension authors and partners and will be highly technical in nature.
Visual Studio ships with Newtonsoft.Json and extension authors can use it too. However, it can be confusing to understand what version to use, how binding redirects work and whether to ship Newtonsoft.Json in the extension itself. This post helps to clarify how it all works.
Explains how Visual Studio versioning works, how extenders should think about it, why there is no Visual Studio version 13.0, and why the year 2213 is the closest we’ll ever get to an alignment again.