Launching Today! Visual Studio 2019 v16.6 & v16.7 Preview 1

Spread the love
Jacqueline Widdis

Jacqueline

Microsoft Build 2020 starts today! Our whole Visual Studio group has been excitedly awaiting this virtual occasion as it represents fantastic effort and devotion from all of our team members and partners. We prepare for the announcements and presentations showcased today will impact your work. As a result, we and are eager to hear your favorites. The first releases out of our office are Visual Studio 2019 variation 16.6 and 16.7 Preview 1. Both of these have efficiency functions to detail in a moment, but we have one more big announcement. Visual Studio Codespaces, our cloud-hosted advancement environments that enable you to leverage the power of the cloud for your edit-build-debug cycle, is in personal preview. The next steps are to discover more about Visual Studio Codespaces and sign-up

While you take in a virtual Build 2020 session, why not download our latest variation of Visual Studio 2019 and let us know what you believe?

New in Visual Studio 2019 variation 16.6

Very first thing to point out are a number of interesting abilities we have actually formerly laid out in the Visual Studio 2019 variation 166 sneak peek 2 and 166 preview 3 blog sites which are typically available today such as:

  • Improved photo debugging experiences that gets rid of the friction in using the photo debugger for the very first time.
  • INTERNET Async tool for profiling.NET apps.
  • INTERNET Performance Quick Actions and Refactorings
  • Terminal with the ability to open multiple instances, personalize font face and sizes, and instantly create profiles for CMD, PowerShell and WSL distributions.
  • Web Tools brand-new experience for setting up Azure services and emulators
  • A range of brand-new C 20 Standard Library features consisting of a preliminary implementation of The STL Changelog on GitHub includes a detailed list.
Updates for C

Next, our C team wish to highlight the ability to generate Doxygen or XML doc remark stubs instantly by typing either /// or / above functions, or by using the Ctrl / shortcut. These comments now appear in Quick Information, Member List, and Specification Help tooltips as well.

Image 166GAquadraticXMLgen
Produce Doxygen or XML file remark stubs immediately

Windows Types Designer for.NET Core

The Windows Kinds designer for.NET Core jobs is also now offered. The designer has all Windows Types manages except DataGridView and ToolStripContainer which is coming quickly. In addition, all other design performance consists of: drag-and-drop, selection, move and resize, cut/copy/paste/ erase of controls, combination with Residence Window, occasions generation and more!

To allow the designer in Visual Studio 2019, go to Tools > Alternatives > Environment > Sneak Peek Functions and pick the Utilize the sneak peek Windows Forms designer for.NET Core apps alternative.

.NET Core Windows Forms Designer
INTERNET Core Windows Forms Designer

New in Visual Studio 2019 variation 16.7 Sneak Peek 1

Git Performance

When again, we have continued to make further enhancements in the new Git experiences within Visual Studio. We improved the branch picker in the Git tool window by including special icons for remote tracking branches. This permits you to distinguish between regional branches and remote tracking branches. We also added special icon indications to remote branches making it easier to differentiate in between these 3 branch types.

Merge Conflict
Brand-new Icons for Git Branch Management

New Icons for Git Branch Management
New Icons for Git Branch Management
C Address Sanitizer

You can begin utilizing Address Sanitizer in the MSVC toolset for X64 as well as debug setups. The ASAN runtime now supports X64 and debug switches / MTd, / MDd, and / LDd. Our C blog site has more info about how C Address Sanitizer can help you discover memory corruption mistakes quickly

C++ Address Sanitizer
C Address Sanitizer in Visual Studio 2019

Intellisense Code Linter

To assist you much better recognize and fix problems as you compose and modify your code, we have actually consisted of a brand-new IntelliSense code linter to inspect your code as-you-type, deal lightbulb actions, and underline problems via squiggles in the editor window. As this is built on top of IntelliSense, it inspects focus on easily-detected issues and are available faster than those via our other, more complex analysis tools such as Background Code Analysis using MSVC and Clang-Tidy combination.

Image 166GAIntelliSenseCodeLinter
IntelliSense Code Linter

WEB Performance

The very first brand-new addition is a quick action to include a debugger display credit to a class. This allows you to pin homes within the debugger programmatically in your code. Additionally, there is a brand-new code fix for unintentional tasks or contrasts to the same variable.

To give this function a try, location your cursor on the class name and use Ctrl to set off the Quick Actions and Refactorings menu. Select Add ‘DebuggerDisplay’ attribute. This will add the debugger display credit to the top of your class and generate an auto approach that returns ToString() which you can modify to return the property worth you require pinned in the debugger.

Quick Action to Add a Debugger Display Attribute to a Class
Quick Action to Include a Debugger Show Credit To a Class

The next modification can be found in IntelliSense conclusion in DateTime and TimeSpan string literals. You can see conclusion alternatives and descriptions as to what each character suggests with date and time formats including examples. Using Ctrl Area within the DateTime or TimeSpan string will reveal you this function in action.

IntelliSense completion in DateTime and TimeSpan string literals
IntelliSense completion in DateTime and TimeSpan string literals

Another alternative added to the Quick Actions and Refactorings menu, is the ability to include a parameter within the Change Signature dialog. With just a number of clicks, you can pick Modification signature A dialog box will open where you have the ability to include a type and criterion name. You can selected to make the specification needed or choice and set a default worth to the call website or introduce a TODO variable into your code. This allows you to go to each error and call site separately to decide which value to pass. If you wish to skip a particular specification, there is a leave out choice for included flexibility.

Adding Parameters through the Change Signature Dialog Process
Including Criteria through the Change Signature Dialog Process
IntelliCode

IntelliCode has been updated in Visual Studio 2019 16.7 Preview 1, and now offers starred suggestions for function arguments. This takes place as a natural procedure while you’re writing C# code. It can’t get much easier to offer this function a try. Simply begin editing your C# code!

XAML Tooling Improvements WPF, UWP, & Xamarin.Forms

Originating From our XAML team are numerous brand-new features for designers who develop applications using XAML such as WPF, UWP, and where relevant, Xamarin.Forms. These features include a new color visualizer in the code editor and an early sneak peek of a new XAML Designer function called Recommended Actions

We ‘d likewise like to highlight two new features designed to improve a XAML designer’s capability to discover a binding failure has occurred in their running application. The failure information are displayed in a new devoted panel. Particularly, we have actually included:

  • New XAML Binding failure sign icon to the in-app toolbar for WPF and UWP applications. This icon will redden if at least one binding failure is spotted. Hovering your mouse over icon will reveal you the overall number failures in the tooltip. Clicking the icon will take you to the new XAML Binding Failures panel.
  • New XAML Binding Failures panel takes the binding failures that were previously only offered in the Output window and makes them simple to examine in the brand-new devoted panel. The panel adds functions such as sorting, searching, and grouping of comparable errors. This panel works for WPF, UWP, and Xamarin.Forms projects. Please note, this needs Xamarin version 4.5.0.266- pre3 or greater.
XAML Developer Ability to Detect Binding Failures
XAML Developer Capability to Detect Binding Failures
Define Playlists Dynamically in Test Explorer

In our Test Explorer, there is brand-new functionality to define playlists dynamically based on Job, Class or Namespace. This suggests you can set up a playlist to include whatever in among these choices. Therefore, any brand-new test contributed to that particular group will instantly be included in your playlist!

To utilize this feature, produce a playlist by right clicking on a Job, Class or Namespace grouping in the Test Explorer and select Contribute To Playlist

Test Explorer Add to Playlist Option
Test Explorer Contribute To Playlist Option

Edit what groups are included in the playlist by clicking the edit button in the tool bar. This will raise check boxes to customize the groups to your desire. This provides you excellent flexibility in your screening.

Test Explorer with Check Boxes for Flexibility
Test Explorer with Check Boxes for Versatility

Accordingly, rather of being a fixed list of tests, these playlists dynamically upgrade based on the defined rules. If you wish to better understand what rules are producing your dynamic playlist, save the playlist file to disk with the Conserve button and view the rules created in the XML.

View Generated Rules in the XML
Test Explorer view XML Rules

You have total flexibility to consist of or leave out individual tests and the playlist. You will have the ability to either upgrade its vibrant rules or switch back to a static list. Also, you can likewise use qualities to specify a dynamic group by modifying the playlist XML straight.

Variation 16.7: Our Next Servicing Baseline

When variation 16.7 transfer to the release channel later on this year, it will be the 3rd “ servicing baseline” for Visual Studio2019 Maintenance standards offer big companies increased versatility over when they can embrace the brand-new features in small version updates that are included in the Business and Professional editions. Unlike standard minor variation releases like 16.5 and 16.6 which get maintenance fixes just up until the next small upgrade is released, we will provide fixes for servicing baselines for 12 months after the next servicing baseline is stated.

As 16.4 is the 2nd maintenance standard, it will continue to get servicing fixes for one year after variation 16.7 releases later on this year. Complete information can be found at Visual Studio Item Lifecycle and Servicing

We Look Forward to your Feedback!

From here, it is time to say just how much our groups are always enjoyed have such a dynamic, participatory community. Please continue to stay active in our Designer Community as we look here initially for ideas and issues. Your excitement around our tools assist inspire each people to constantly provide new experiences to sustain your creativity in the designer space. Even if we can’t be together face to face for Build 2020 this year, we hope you still have a fantastic experience with virtual sessions, product presentations, and the cooperation of our neighborhood towards a better world.

Find Out More