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.
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.
At //BUILD 2017, we shipped an update to the Continuous Delivery Tools for Visual Studio. This update has support for configuring a Continuous Integration and Continuous Delivery pipeline for ASP.NET Core projects with container support to an existing Azure Service Fabric cluster directly from Visual Studio 2017. To configure continuous delivery...
We are looking to improve your experience on the Visual Studio Blog. It would be very helpful if you could share your feedback via this short survey that should take less than 2 minutes. Thanks! At //BUILD 2017, we shipped an update to the Continuous Delivery Tools for Visual Studio with support for configuring a Continuous Integration and ...
