{"id":29049,"date":"2020-07-29T10:15:56","date_gmt":"2020-07-29T17:15:56","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/dotnet\/?p=29049"},"modified":"2020-07-28T15:43:44","modified_gmt":"2020-07-28T22:43:44","slug":"learn-about-the-latest-net-productivity-features","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/learn-about-the-latest-net-productivity-features\/","title":{"rendered":"Learn about the latest .NET Productivity features"},"content":{"rendered":"
The .NET Productivity team (a.k.a. Roslyn) is constantly thinking of new ways to make .NET developers more productive. We\u2019ve been working hard to take the feedback you\u2019ve sent us and turn it into tools that you want! In this post, I\u2019ll cover some of the latest .NET productivity features available in Visual Studio 2019<\/a>.<\/div>\n

<\/p>\n

Tooling\u00a0improvements<\/h3>\n
<\/div>\n
The feature that I\u2019m most excited about is the IntelliSense completion in DateTime and TimeSpan string literals<\/a>. This feature is extremely helpful because we all know remembering DateTime and TimeSpan formats is hard enough. Place your caret inside the DateTime or TimeSpan string literal and press (Ctrl + Space). You’ll then see completion options and an explanation as to what each character means.\"IntelliSense<\/div>\n

<\/p>\n

Add file header<\/a> allows you to easily add file headers to existing files, projects, and solutions using EditorConfig<\/a>. You’ll first need to add the file_header_template<\/em> rule to your .editorconfig<\/em> file. Then, set the value to equal the header text you’d like applied. Next, place your caret on the first line of any C# or Visual Basic file. Press (Ctrl<\/strong>+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu and select Add file header<\/strong>.<\/p>\n

\"Add<\/div>\n

<\/p>\n

The change method signature<\/a> dialog now allows you to add a parameter. Place your caret within the method\u2019s signature. Press (Ctrl<\/strong>+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu and select Change signature<\/strong>. The following dialog will open where you can now select Add<\/strong> to add a parameter.<\/p>\n

\"Change<\/div>\n

\nOnce you select Add<\/strong>, the new Add Parameter<\/strong>\u00a0dialog opens. The Add Parameter dialog allows you to add a type name and a parameter name. You can choose to make the parameter required or optional with a default value. You can then add a value at the call site and choose a named argument for that value or you can introduce a TODO variable. The TODO variable puts a TODO in your code so you can visit each error and go through each call site independently and decide what to pass. For optional parameters you have the option to omit the call site completely.<\/p>\n

\"Add<\/div>\n

<\/p>\n

Code\u00a0fixes\u00a0and\u00a0refactorings<\/h3>\n
\n
Code fixes and refactorings are the code suggestions the compiler provides through the light bulb and screwdriver icons. To trigger the Quick Actions and Refactorings<\/strong> menu, press (Ctrl<\/strong>+.<\/strong>) or (Alt<\/strong>+Enter<\/strong>). The following list shows the code fixes and refactorings that are new in Visual Studio 2019:<\/div>\n<\/div>\n

\nThe add explicit cast<\/a> code fix allows you to add an explicit cast when an expression cannot be implicitly cast. Place your caret on the error. Press (Ctrl<\/strong>+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu and select Add explicit cast<\/strong>.<\/p>\n

\"Add<\/div>\n

\nThe simplify conditional expression<\/a> refactoring simplifies conditional expressions to be more legible and concise. Place your caret on the conditional expression. Press (Ctrl<\/strong>+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu and select Simplify conditional expression<\/strong>.<\/p>\n

\"Simplify<\/div>\n

\nHave you ever wished you could easily read or convert to a verbatim string? Now you have a refactoring at your fingertips to convert between regular string and verbatim string literals<\/a>. Place your caret on either the regular string or the verbatim string literal. Press (Ctrl<\/strong>+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu. Next, select from one of the following:<\/p>\n

<\/div>\n

Select Convert to verbatim string<\/strong>:<\/p>\n

\"Convert<\/div>\n

\nSelect Convert to regular string<\/strong>:<\/p>\n

\"Convert<\/div>\n

\nThe add debugger display attribute<\/a> refactoring allows you to pin properties within the debugger programmatically in your code. Place your caret on the class name. Press (Ctrl<\/strong>+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu and select Add ‘DebuggerDisplay’ attribute<\/strong>. This will add the debugger display attribute to the top of your class and generate an auto method that returns ToString(), which you can edit to return the property value you want pinned in the debugger.<\/p>\n

\"Add<\/div>\n

\nThe generate comparison operators<\/a> refactoring generates a boilerplate code with comparison operators for types that implement IComparable. Place your caret either inside the class or on IComparable. Press (Ctrl<\/strong>+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu and select Generate comparison operators<\/strong>.<\/p>\n

\"Generate<\/div>\n

\nThe generate IEquatable operators<\/a> refactoring automatically adds the IEquatable as well as the equals and not equals operators for structs. Place your caret within the struct. Press (Ctrl<\/strong>+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu and select Generate Equals(object)<\/strong>.<\/p>\n

\"Generate<\/div>\n

\nThe generate properties when generating a constructor<\/a> allows you to easily create a constructor with properties in a type. Place your caret on the instance. Press (Ctrl<\/strong>+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu and select Select Generate constructor in <QualifiedName> (with properties)<\/strong>.<\/p>\n

\"Generate<\/div>\n

\nThere’s now an easy fix for accidental assignments and comparisons. Place your caret on the warning. Press (Ctrl<\/strong>+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu. Next, select from one of the following options:<\/p>\n

<\/div>\n

For accidental assignments, select Assign to ‘<QualifiedName>.value’<\/strong>:<\/p>\n

\"Accidental<\/div>\n

\nFor accidental comparisons, select Compare to ‘<QualifiedName>.value’<\/strong>:<\/p>\n

\"Accidental<\/div>\n

\nThe null suppression operator warning and code fix helps you to easily identify and fix a suppression operator that has no effect. For example, in this case someone wanted to express that something isn’t `string` and typed `!is string` instead of `is not string`. The `!` is legal but is interpreted as asserting the expression on the left as is not `null`. Since that can be confusing, we now offer a warning and code fix. Place your caret on the suppression operator. Press (Ctrl<\/strong>+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong>\u00a0menu. Next, select from one of the following:<\/p>\n

<\/div>\n

To remove the operator completely, select Remove operator (preserves semantics)<\/strong>:<\/p>\n

\"Remove<\/div>\n

\nTo negate the expression, select Negate expression (change semantics)<\/strong>:<\/p>\n

\"Negate<\/div>\n

<\/p>\n

Get involved<\/h3>\n
\n
\n
This was just a sneak peek of what’s new in Visual Studio 2019<\/a>. For a complete list of what’s new, see the release notes<\/a>. And feel free to provide feedback on the Developer Community<\/a> website, or using the Report a Problem<\/a> tool in Visual Studio.<\/div>\n<\/div>\n<\/div>\n
<\/div>\n","protected":false},"excerpt":{"rendered":"

The .NET Productivity team (a.k.a. Roslyn) is constantly thinking of new ways to make .NET developers more productive. We\u2019ve been working hard to take the feedback you\u2019ve sent us and turn it into tools that you want! In this post, I\u2019ll cover some of the latest .NET productivity features available in Visual Studio 2019. Tooling\u00a0improvements […]<\/p>\n","protected":false},"author":5818,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[685],"tags":[],"class_list":["post-29049","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dotnet"],"acf":[],"blog_post_summary":"

The .NET Productivity team (a.k.a. Roslyn) is constantly thinking of new ways to make .NET developers more productive. We\u2019ve been working hard to take the feedback you\u2019ve sent us and turn it into tools that you want! In this post, I\u2019ll cover some of the latest .NET productivity features available in Visual Studio 2019. Tooling\u00a0improvements […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/29049","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/5818"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=29049"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/29049\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=29049"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=29049"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=29049"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}