In this post I\u2019ll cover the following .NET productivity enhancements:<\/p>\n
- \n
- Navigate to source code<\/li>\n
- Stack Trace Explorer<\/li>\n
- Naming Styles in the EditorConfig UI<\/li>\n
- Sync namespaces from Solution Explorer<\/li>\n
- IntelliSense completion for await<\/li>\n
- New Code Fixes and Refactorings<\/li>\n<\/ul>\n
Navigation and code exploration<\/h3>\n
Navigating and exploring code is an integral part of developer productivity. In Visual Studio 2022 we now surface embedded source and Source Link<\/a> as part of Go To Definition. This allows you to navigate to original source files that declare the target symbol that isn’t in your current solution. Place your cursor on a symbol and press F12<\/strong> to navigate to the original source code.<\/p>\n
![\"Source](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/GTDSourceLink.gif\")
<\/a><\/p>\nA new Stack Trace Explorer Window displays stack traces allowing you to click and navigate directly to the related code. You can copy a stack trace from your solution and paste it into the Stack Trace Explorer window to get started. To open the Stack Trace Explorer window, go to View <\/strong>> Other Windows<\/strong> and select Stack Trace Explorer<\/strong> or use the shortcut Ctrl+E<\/strong>, Ctrl+S<\/strong>.<\/p>\n
![\"Stack](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/17.1_P2_stack_trace_explorer.gif\")
<\/a><\/p>\nWe added a new command called Value Tracking allowing you to perform data flow analysis on your code to help you quickly determine how certain values might have passed at a given point. Value Tracking is available on any member in the context (right-click) menu by selecting the Track Value Source<\/strong> command. The Track Value Source command will open the Value Tracking window allowing you to analyze results.<\/p>\n
![\"Value](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/Value-tracking.png\")
<\/a><\/p>\nWe added an option to underline variables that are reassigned. This is off by default so you will need to enable it in Tools<\/strong> > Options <\/strong>> Text Editor<\/strong> > C#<\/strong> or Basic <\/strong>> Advanced<\/strong> and select Underline reassigned variables<\/strong>. This helps reassigned variables stand out from other variables in the same local scope.<\/p>\n
![\"Underline](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/reassigned-variables.png\")
<\/a><\/p>\nThe Code Definition Window now supports C# and Visual Basic allowing you to quickly understand and explore code. To use the Code Definition Window, select View <\/strong>> Window <\/strong>> Code Definition<\/strong>. Next, place your cursor on an identifier to navigate and explore code.<\/p>\n
![\"The](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/code-definition-window2.png\")
<\/a><\/p>\nIn C# 8.0 we introduced nullable reference types<\/a> allowing you to declare whether null is expected. To use nullable reference types you either need to add the <Nullable>enable<\/Nullable>\u00a0<\/strong>element to your project file or add the #nullable enable<\/strong> pragma to every source file in your project. To help streamline this process we now automatically include the <Nullable>enable<\/Nullable><\/strong> for new .NET projects. For existing .NET projects that target .NET Core 3.1 or newer, we offer a new refactoring to enable nullable reference types<\/a> across a project. Place your cursor on a #nullable enable<\/strong> pragma and press (Ctrl+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu. Select Enable nullable reference types in a project<\/strong>.<\/p>\n
![\"Enable](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/17.1_P1_net_productivity_enable_nullable_refactoring.png\")
<\/a><\/p>\nIntelliSense completion<\/h3>\n
IntelliSense is a code-completion aid that includes a number of features: List Members, Parameter Info, Quick Info, and Completion. We recently added IntelliSense completion for await within an awaitable expression. Start typing an awaitable expression and notice how await will now show up in the completion list.<\/p>\n
![\"Async](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/async-completion2.gif\")
<\/a><\/p>\nIf you want to learn more about recent additions to IntelliSense including AI helping you code, check out the IntelliCode docs<\/a>.<\/p>\n
Code fixes & refactorings<\/h3>\n
Visual Studio provides hints to help you maintain and modify your code in the form of code fixes and refactorings. These appear as lightbulbs and screwdrivers next to your code or in the margin. The hints can resolve warnings and errors as well as provide suggestions. You can open these suggestions by typing (Ctrl+.<\/strong>) or by clicking on the lightbulb or screwdriver icons.<\/p>\n
You can check out the most popular refactorings that are built in to Visual Studio at https:\/\/aka.ms\/refactor. We\u2019ve added a bunch of new code fixes and refactorings in Visual Studio 2022! Here are some of our favorites.<\/p>\n
- \n
- Introduce parameter<\/li>\n
- File scoped namespace<\/li>\n
- Use tuple to swap values<\/li>\n
- Move static members<\/li>\n
- Simplify property pattern<\/li>\n
- Prefer null check over type check<\/li>\n
- Sync namespaces<\/li>\n<\/ul>\n
The introduce parameter<\/strong> refactoring will move an expression from a method implementation to its callers by adding a new parameter.\u00a0Place your cursor on\u00a0the line containing the expression or highlight the expression.\u00a0Press (Ctrl+.<\/strong>) to trigger the\u00a0Quick Actions and\u00a0Refactorings\u00a0<\/strong>menu.\u00a0Select\u00a0Introduce\u00a0parameter for {0}<\/strong>\u00a0or\u00a0Introduce parameter for all occurrences of {0}<\/strong>.\u00a0Both options will have three flyout options to either (1) insert the updated expression at all the\u00a0call sites, (2) extract and create a new method that returns the expression and adds an argument at the\u00a0call sites, or (3) create an overload of the method that contains the expression and calls upon the original method.<\/p>\n
![\"Introduce](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/introduce-parameter.png\")
<\/a><\/p>\nIn C# 10.0 we introduced file-scoped namespace<\/a> so you no longer need to nest class definitions within a namespace. To use file-scoped namespace, make sure your project targets the .NET 6.0 SDK or you can set the language version in your project file to 10.0.\u00a0Place your cursor on a namespace. Press (Ctrl+.<\/strong>) to trigger the\u00a0Quick Actions and\u00a0Refactorings\u00a0<\/strong>menu.\u00a0Select Convert to file-scoped namespace<\/strong>.<\/p>\n
![\"File](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/file-scoped-namespace-dark-theme.png\")
<\/a><\/p>\nThere is a new refactoring that detects variable swaps and suggests using a tuple to swap values instead of using a temporary variable in-order to swap arguments. Place your cursor on a temporary variable assignment where you are swapping values. Press (Ctrl+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu. Select Use tuple to swap values<\/strong>.<\/p>\n
![\"Use](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/use-tuple-to-swap-values.png\")
<\/a><\/p>\nYou can more easily move static members to a new type. Place your cursor on a static member. Press (Ctrl+.<\/strong>) to trigger the Quick Actions and Refactorings<\/strong> menu. Select Move static members to another type<\/strong>. This will open a dialog where you can select the members that you would like to move.<\/p>\n
![\"Move](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/move-static-members.png\")
<\/a><\/p>\nThe simplify code to use the new C# 10.0 extended property patterns refactoring reduces noise allowing you to reference nested members instead of nesting another recursive pattern. Place your cursor on a nested member reference. Press (Ctrl+.<\/strong>) to trigger the\u00a0Quick Actions and\u00a0Refactorings<\/strong>\u00a0menu.\u00a0Select\u00a0Simplify property pattern<\/strong>.<\/p>\n
![\"Simplify](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/simplify-property-pattern.png\")
<\/a><\/p>\nThere is now a refactoring to prefer is not null<\/em> over is object<\/em> when applied to value types. To use this new refactoring place your cursor on a type check. Press (Ctrl+.<\/strong>) to trigger the\u00a0Quick Actions and\u00a0Refactorings\u00a0<\/strong>menu.\u00a0Select Prefer ‘null’ check over type check<\/strong>.<\/p>\n
![\"Prefer](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/prefer-is-null-over-is-object.png\")
<\/a><\/p>\nYou can also invoke code fixes and refactorings from the Solution Explorer (right-click) menu. One of our most popular refactorings is sync namespaces allowing you to synchronize namespaces to match your folder structure. The Sync Namespaces<\/strong> command is now available in the (right-click) menu of a project in Solution Explorer. Selecting Sync Namespaces will automatically synchronize namespaces to match your folder structure.<\/p>\n
![\"Sync](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/sync-namespaces-dark.png\")
<\/a><\/p>\nCode style enforcement<\/h3>\n
Enforcing consistent code style is important as developer teams and their code bases grow. You can configure code styles with EditorConfig<\/a>! EditorConfig files help to keep your code consistent by defining code styles and formats. These files can live with your code in its repository and use the same source control. This way the style guidance is the same for everyone on your team who clones from that repository. With EditorConfig files you can enable or disable individual .NET coding conventions and configure the severity to which you want each rule enforced.<\/p>\n
In Visual Studio 2019 we introduced a new UI for EditorConfig\u00a0allowing you to easily view and configure every available .NET coding convention. In this release we added Naming Styles to the EditorConfig UI. Naming Styles allow you to enforce naming conventions in your code such as interfaces should always start with the letter \u201cI\u201d. To add an EditorConfig file to a project or solution:\u00a0<\/span><\/p>\n
- \n
- Right-click on the project or solution name within the Solution Explorer.<\/li>\n
- Select Add New Item<\/strong>.<\/li>\n
- In the Add New Item <\/strong>dialog, search for EditorConfig.<\/li>\n
- Select the .NET EditorConfig template to add an EditorConfig file prepopulated with default options.<\/li>\n<\/ul>\n
![\"Naming](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/12\/naming_styles-1.png\")
<\/a><\/p>\nYou can also add a new EditorConfig file from the command line by typing dotnet new editorconfig.<\/a><\/em> To use dotnet new editorconfig<\/em>\u00a0make sure your project targets the .NET 6.0 SDK or later. Next, open the Visual Studio integrated terminal by pressing (Ctrl+`<\/strong>). You can then run dotnet new editorconfig<\/em> to add a new EditorConfig file to your project.<\/p>\n
Thank you<\/h3>\n
Last, but certainly not least, a big Thank You to the following people who contributed to Roslyn. Ultimately, you’ve helped make Visual Studio 2022 awesome.<\/p>\n
- \n
- AlFas (@AlFasGD)<\/a>: Fix unused Update parameter (PR #56741<\/a>)<\/li>\n
- Petr Onderka (@svick)<\/a>: Don’t suggest simplification for positional patterns (PR #57676<\/a>)<\/li>\n
- Adam Speight (@AdamSpeight2008)<\/a>: Simplify the Lambda Functions (PR #51731<\/a>)<\/li>\n
- Martin Strecker (@MaStr11<\/a>):\n
- \n
- Provide quick info at #regionend showing #region message (PR #56609<\/a>)<\/li>\n
- Completion: Suggest “await” after dot of awaitable expression (PR #55817<\/a>)<\/li>\n
- Codefix for CS1591: Add inheritdoc (PR #57004<\/a>)<\/li>\n<\/ul>\n<\/li>\n
- Youssef Victor (@Youssef1313)<\/a>:\n
- \n
- Remove redundant check in IsGlobalMain (PR #55395<\/a>)<\/li>\n
- Attempt to mark EqualityContract property accessor as not auto-implemented (PR #57917<\/a>)<\/li>\n
- Minor refactoring in SettingsUpdateHelper (PR #55123<\/a>)<\/li>\n
- Fix spacing when generating editorconfig options from UI (PR #54601<\/a>)<\/li>\n<\/ul>\n<\/li>\n
- Pavel Krymets (@pakrym)<\/a>: Do not normalize leading whitespace in code comments (PR #57414<\/a>)<\/li>\n
- Kev Ritchie (@KevRitchie)<\/a>: Update documentation to explain FullyQualifiedFormat behavior (PR #57397<\/a>)<\/li>\n
- Marcio A Braga (@MarcioAB)<\/a>: Update TextSpan.cs (PR #57300<\/a>)<\/li>\n
- Bernd Baumanns (@bernd5)<\/a>: Fix for “Function pointer invocation has “None” IOperation” (PR #57191<\/a>)<\/li>\n
- Paul M Cohen (@paul1956)<\/a>: Initial fix for issue “VB Formatting of LineContinuation Wrong after _ ‘ Comment” (PR #54559<\/a>)<\/li>\n
- Saleh Ahmed Panna (@panna-ahmed)<\/a>: Localized missing warning message (PR #57502<\/a>)<\/li>\n<\/ul>\n
Get involved<\/h3>\n
This was just a sneak peak of what\u2019s new in\u00a0Visual Studio 2022<\/a>. For a complete list of what\u2019s new, see the\u00a0release notes<\/a>. And feel free to provide feedback on the\u00a0Developer Community<\/a>\u00a0website, or using the\u00a0Report a Problem<\/a>\u00a0tool in Visual Studio.<\/p>\n","protected":false},"excerpt":{"rendered":"
With the release of Visual Studio 2022 the Roslyn team continues to enhance your .NET developer productivity with the latest tooling improvements. In this post I\u2019ll cover the following .NET productivity enhancements: Navigate to source code Stack Trace Explorer Naming Styles in the EditorConfig UI Sync namespaces from Solution Explorer IntelliSense completion for await New […]<\/p>\n","protected":false},"author":5818,"featured_media":228872,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[155],"tags":[],"class_list":["post-235905","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-visual-studio"],"acf":[],"blog_post_summary":"
With the release of Visual Studio 2022 the Roslyn team continues to enhance your .NET developer productivity with the latest tooling improvements. In this post I\u2019ll cover the following .NET productivity enhancements: Navigate to source code Stack Trace Explorer Naming Styles in the EditorConfig UI Sync namespaces from Solution Explorer IntelliSense completion for await New […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/235905","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/5818"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=235905"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/235905\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/228872"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=235905"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=235905"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=235905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Attempt to mark EqualityContract property accessor as not auto-implemented (PR #57917<\/a>)<\/li>\n
- Completion: Suggest “await” after dot of awaitable expression (PR #55817<\/a>)<\/li>\n
- Petr Onderka (@svick)<\/a>: Don’t suggest simplification for positional patterns (PR #57676<\/a>)<\/li>\n
- In the Add New Item <\/strong>dialog, search for EditorConfig.<\/li>\n