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 and hopefully eliminate any confusion about the correct use patterns for extension authors.
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.
Welcome to February update of Java on Visual Studio Code! We’d like to share a few new improvements to further enhance your productivity, including
- Dependency auto-completion and more Maven updates
- Performance improvements
- Standalone file supports
- Multiple source folders support
- Easy launch for multi-main-class projects
- Hide temporary files
- Bulk generate getters and setters
- Test configuration and report update
- Including IntelliCode to Java Extension Pack
Try these new features by installing Java Extension Pack with Visual Studio Code.
Do you want to try the preview of Visual Studio 2019 but worry that your favorite extensions aren’t supported yet? A record number of extensions have already added support for Visual Studio 2019. So there is a good chance your favorite extensions are among them. In fact, more than 850 extensions are currently available, and more are being updated every day.
What if the community of extension authors banded together to add powerful features to Visual Studio that made it easier to create extensions? That’s the idea behind Extensibility Essentials – an extension pack that ships community-recommended extensions for extension authors.
Visual Studio extensions can now be marked with a Preview label which is shown very clearly on the Visual Studio Marketplace. This gives your customers clear expectations that this version could contain issues as you are actively developing new features. Learn how to enable the Preview label here.
Visual Studio 2017 version 15.8 made it possible to use the PackageReference syntax to reference NuGet packages in Visual Studio Extensibility (VSIX) projects. This makes it much simpler to reason about NuGet packages and opens the door for having a complete meta package containing the entire VSSDK.
Recently, I’ve updated over 30 of my extensions to support Visual Studio 2019 (16.0). To make sure they work, I got my hands on a very early internal build of VS 2019 to test with (working on the Visual Studio team has its benefits).
I’m often asked how to best learn to build Visual Studio extensions, so here is what I wished someone told me before I got started.
Don’t skip the introduction
It’s easy to create a new extensibility project in Visual Studio,
The Visual Studio team partners with extension authors to provide a productive development environment for users, who rely on a rich ecosystem of quality extensions. Today, we’re introducing an update to extension auto load based on feedback from our community of developers,