{"id":30769,"date":"2020-11-18T10:05:41","date_gmt":"2020-11-18T17:05:41","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/dotnet\/?p=30769"},"modified":"2020-11-17T13:25:13","modified_gmt":"2020-11-17T20:25:13","slug":"whats-new-in-net-productivity","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/whats-new-in-net-productivity\/","title":{"rendered":"What’s new in .NET Productivity"},"content":{"rendered":"

The .NET Productivity team (a.k.a. Roslyn) wants to help you be more productive! We\u2019ve seen a lot of excitement in the past few months over our latest features which automate and reduce editing tasks to a single click and help save you time. In this post, I\u2019ll cover some of the latest .NET productivity features available in Visual Studio 2019<\/a>.<\/p>\n

Tooling improvements<\/h2>\n

Starting in .NET 5.0, Roslyn analyzers are included with the .NET SDK<\/a>. Roslyn analyzers are enabled, by default, for projects that target .NET 5.0 or later. You can enable them on projects that target earlier .NET versions by setting the EnableNETAnalyzers<\/a> property to true<\/em>. You can also use the Project Properties to enable\/disable .NET analyzers. To access the Project Properties, right-click on a project within Solution Explorer and select Properties. Next, select the Code Analysis tab where you can either select or clear the checkbox to Enable .NET analyzers.<\/p>\n

\"Project<\/p>\n

Another exciting feature is inline parameter name hints<\/a> that inserts adornments for literals, casted literals, and object instantiations prior to each argument in function calls. In 16.9 Preview 1, we also added inline type hints for variables with inferred types and lambda parameter types. You\u2019ll first need to turn this option on in Tools<\/em> > Options<\/em> > Text Editor<\/em> > C#<\/em> or Basic<\/em> > Advanced<\/em> and select Display inline parameter name hints<\/strong> and Display inline type hints<\/strong>. You can also use the shortcut Alt<\/strong>+F1<\/strong> to briefly view hints.<\/p>\n

\"Inline<\/p>\n

You can now extract members from a selected class to\u202fa\u202fnew base class with the new\u202fextract base class<\/a>\u202frefactoring.\u202fPlace your cursor on either the class name or a highlighted member. Press Ctrl<\/strong>+.<\/strong> to trigger the Quick Actions and Refactorings<\/strong> menu. Select\u202fPull member(s) up to new base class<\/strong> or Extract base class<\/strong>.\u202fThe\u202fnew\u202fExtract\u202fBase\u202fClass<\/strong>\u202fdialog will open where you can specify the name for the base class and location of where it should be placed. You can select the members that you want to transfer to the new base class and choose to make the members abstract by selecting the checkbox in the\u202fMake\u202fabstract<\/strong>\u202fcolumn.<\/p>\n

\"Extract<\/p>\n

Code cleanup<\/a> has new configuration options that can apply formatting and file header preferences set in your EditorConfig<\/a> file across a single file or an entire solution.<\/p>\n

\"Code<\/p>\n

Code fixes and refactorings<\/h2>\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:<\/p>\n

The inline method<\/a> refactoring helps you replace usages of a static, instance, and extension method within a single statement body with an option to remove the original method declaration. Place your cursor on the usage of the method. Press Ctrl<\/strong>+.<\/strong> to trigger the Quick Actions and Refactorings<\/strong> menu. Next select from one of the following options:<\/p>\n

Select Inline <QualifiedMethodName><\/code><\/strong> to remove the inline method declaration:<\/p>\n

\"Inline<\/p>\n

Select Inline and keep <QualifiedMethodName><\/code><\/strong> to preserve the original method declaration:<\/p>\n

\"Inline<\/p>\n

The use pattern matching<\/a> refactoring introduces the new C# 9 pattern combinators. Along with the pattern matching suggestions, such as converting ==<\/code> to use is<\/code> where applicable, this code fix also suggests the pattern combinators and<\/code>, or<\/code> and not<\/code> when matching multiple different patterns and negating. Place your cursor inside the statement. Press Ctrl<\/strong>+.<\/strong> to trigger the Quick Actions and Refactorings<\/strong> menu and select Use pattern matching<\/strong>.<\/p>\n

\"Use<\/p>\n

The make class abstract<\/a> refactoring allows you to easily make a class abstract when you\u2019re trying to write an abstract method in a class that isn\u2019t abstract. Place your cursor on the method error. Press Ctrl<\/strong>+.<\/strong> to trigger the Quick Actions and Refactorings<\/strong> menu and select Make class \u2018abstract\u2019<\/strong>.<\/p>\n

\"Make<\/p>\n

The convert typeof to nameof<\/a> refactoring allows you to easily convert instances of typeof(<QualifiedType><\/code>).Name<\/em> to nameof(<QualifiedType><\/code>)<\/em> in C# and instances of GetType(<QualifiedType><\/code>).Name<\/em> to NameOf(<QualifiedType><\/code>)<\/em> in Visual Basic. Using nameof<\/em> instead of the name of the type avoids the reflections involved when retrieving an object. Place your cursor within the typeof(<QualifiedType><\/code>).Name<\/em>. Press Ctrl<\/strong>+.<\/strong> to trigger the Quick Actions and Refactorings<\/strong> menu and select\u202fConvert\u202f’typeof’\u202fto\u202f’nameof’<\/strong>.<\/p>\n

\"Convert<\/p>\n

Visual Basic had multiple ways of passing parameters, ByVal<\/em> and ByRef<\/em>, and for a long time ByVal<\/em> has been optional. We now fade ByVal<\/em> to say it’s not necessary along with a code fix to remove the unnecessary ByVal<\/em>. Place your cursor on the ByVal keyword. Press Ctrl<\/strong>+.<\/strong> to trigger the Quick Actions and Refactorings<\/strong> menu and select \u2018ByVal\u2019 keyword is unnecessary and can be removed<\/strong>.<\/p>\n

\"Remove<\/p>\n

Now, there\u2019s also a code fix to remove the in<\/code> keyword where the argument shouldn\u2019t be passed by reference. Place your cursor on the error. Press Ctrl<\/strong>+.<\/strong> to trigger the Quick Actions and Refactorings<\/strong> menu and select Remove \u2018in\u2019 keyword<\/strong>.<\/p>\n

\"Remove<\/p>\n

In 16.9 Preview 1, we also added a code fix that removes redundant equality expressions for both C# and Visual Basic. Place your cursor on the redundant equality expression. Press Ctrl<\/strong>+.<\/strong> to trigger the Quick Actions and Refactorings<\/strong> menu and select Remove redundant equality<\/strong>.<\/p>\n

\"Remove<\/p>\n

And the last refactoring we added in 16.9 Preview 1 suggests using \u2018new(\u2026)\u2019<\/a> in non-contentious scenarios. Place your cursor on the field declaration. Press Ctrl<\/strong>+.<\/strong> to trigger the Quick Actions and Refactorings<\/strong> menu and select Use ‘new(\u2026)’<\/strong>.<\/p>\n

\"Use<\/a><\/p>\n

Get involved<\/h2>\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. You can also share your feedback with us on GitHub<\/a> or tweet @roslyn, we’d love to hear what you think!<\/p>\n","protected":false},"excerpt":{"rendered":"

Learn about the latest .NET Productivity features!<\/p>\n","protected":false},"author":5818,"featured_media":30773,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[685,196,756,646],"tags":[4,7198,311,316,7197],"class_list":["post-30769","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dotnet","category-dotnet-core","category-csharp","category-visual-studio","tag-net","tag-net-5-0","tag-code-fixes","tag-refactoring","tag-tooling-improvements"],"acf":[],"blog_post_summary":"

Learn about the latest .NET Productivity features!<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/30769","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=30769"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/30769\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/30773"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=30769"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=30769"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=30769"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}