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.
This blog post is all about the cool new features, bug fixes and performance improvements we've added to the latest release (Preview 3) of Visual Studio 2019 for Mac. Some of the highlights include but are not limited to the following: launching multiple IDE instances, faster Xamarin Android developer tools, and a new C# editor. Read on to learn more.
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.
Over the last few months, we’ve seen lots of thoughtful and passionate discussion throughout the community, on the blog, in Developer Community, and a bunch of social media sites. There were a few popular themes in the feedback that we wanted to acknowledge and talk a bit about the changes we’ve already made based on your feedback.
Are you inspecting many variables at once in the Locals window? Tired of constantly scrolling through the Watch window to locate the object you are currently interested in? New to Visual Studio 2019, you can now find your variables and their properties faster using the new search feature found in the Watch, Autos, and Locals windows!
To ensure that the tools you need are close at hand, we’ve updated the Cloud Explorer for Visual Studio extension for IoT developers to enable you to view your Azure IoT Hubs, inspect their properties, and perform other actions from within Visual Studio. Cloud Explorer is installed by default if you selected the Azure Workload when installing Visual Studio.
Check out the UI and UX changes coming to Visual Studio 2019. The Design Team working on Visual Studio would love to hear what you think.
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.
Customer feedback is a critical input to help us improve Visual Studio. Up until two years ago, the Visual Studio customer feedback system left room for improvement – customers could use the “send a smile” feature in Visual Studio, but this would result in only coarse-grained feedback such as “I like this” or “I don’t like this.” The feedback we got through this UI then went into a database our team accessed,