Today we’re excited to announce the private preview of a set of developer services that enable you to work from anywhere, and on any device, complete with the most intelligent productivity and collaboration tools in the industry.
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.
A few days ago, we announced the general availability of Visual Studio 2019. But I’ve been using Visual Studio 2019 exclusively since the first internal build – long before the release of Preview 1 in December of 2018. During this time, there has been a lot of little features that have put a smile on my face and made me more productive. I want to share a few of them with you.
Today we’re excited to announce Visual Studio Live Share for generally availability and included with Visual Studio 2019! This is the culmination of over a year of hearing your feedback and building a product that enhances the many diverse ways you and your team collaborate. Regardless of whether your team is fully remote, partially distributed, or entirely co-located, we want to make your collaboration experiences more enjoyable and productive with Live Share.
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.
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
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.