{"id":235984,"date":"2022-01-05T11:39:58","date_gmt":"2022-01-05T19:39:58","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=235984"},"modified":"2022-01-07T07:13:22","modified_gmt":"2022-01-07T15:13:22","slug":"visual-studio-17-1-preview-2-is-now-available","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/visual-studio-17-1-preview-2-is-now-available\/","title":{"rendered":"Visual Studio 17.1 Preview 2 is now available!"},"content":{"rendered":"

Today, we\u2019re releasing Visual Studio 2022 17.1 Preview 2. We\u2019ve continued to iterate on the themes of the Visual Studio 2022 release and have enhanced existing features, brought new productivity improvements, and made it easier for you to make Visual Studio your own. In this blog post, we\u2019ll talk in detail about changes in the Git, Search and Navigation, C++, and .NET experiences as well as some new capabilities for personalizing colored tabs. For more information on everything in this release, see the Visual Studio 17.1 Preview 2 release notes<\/a>. To try out everything we\u2019re writing about today, download the Visual Studio 2022 Preview:<\/p>\n

Download Visual Studio 2022 Preview<\/a><\/div><\/p>\n

In addition to these new experiences, we\u2019ve also paid special attention to feedback from you, our community members, and have addressed over a hundred customer-reported issues via Developer Community so far in 17.1. We truly appreciate the time you\u2019ve spent reporting issues and encourage you to continue doing so to help us make 17.1 the most performant, reliable IDE yet. We’re aware many of our users wait for the next release after a major one before updating and there is no better time to download the fastest version of Visual Studio to date.<\/p>\n

Performance work is never done and we strive to do better every release. In 17.1, we\u2019ve optimized Find All reference searches in C++ projects with up to a 22% improvement. As we move forward, we\u2019ll continue our investments in performance throughout the IDE to bring you an overall more responsive experience.<\/p>\n

Be more productive with Git<\/h2>\n

We\u2019re very excited to announce that 17.1 preview 2 comes with long-awaited Git features to enhance your productivity and make your day-to-day work easier! Now, it\u2019s easy to compare your current branch with other branches in your repository, which can be very helpful when you\u2019re preparing for a pull request or even before you delete a branch.<\/p>\n

\"A<\/p>\n

This preview comes with enhanced detached head support and introduces the ability to checkout a commit and checkout the tip of any remote branch. Now you can checkout any commit and go back to a previous point in your repository\u2019s history to run or test your code. You can also quickly review pull requests and evaluate your team\u2019s updates by checking out the tip of any remote branch.<\/p>\n

\"Screenshot<\/p>\n

\"Screenshot<\/p>\n

We continued improving our multi-repo support preview feature by enhancing the inner loop branching experience. Now you can utilize branch pickers on both the status bar and the Git changes tool window to checkout branches and do lightweight branch management across all or your active repositories.<\/p>\n

\"Screenshot<\/p>\n

\"Screenshot<\/p>\n

The create new branch experience now supports creating branches across all active repositories at the same time. You no longer need to manually create branches across repositories.<\/p>\n

\"Screenshot<\/p>\n

This preview also comes with some of our first Line-staging preview functionality. For example, now you can utilize the diff to stage chunks or sections of code.<\/p>\n

\"Screenshot<\/p>\n

If you’d like more information about these Git enhancements, check out the Introducing new Git features to Visual Studio 2022 blog post<\/a>.<\/p>\n

Keep your code clean, automatically!<\/h2>\n

You can now configure personalized Code Cleanup profiles that will automatically run whenever you save a file. This will help minimize stylistic violations within PRs and more by allowing you to spend less time fixing code that doesn\u2019t meet specific standards and more time focusing and being productive.<\/p>\n

To configure your personalized Code Cleanup profiles, navigate to Analyze > Code Cleanup > Configure Code Cleanup.<\/p>\n

\"Screenshot<\/p>\n

To apply a code cleanup profile automatically on save, navigate to Tools > Options > Text Editor > check \u201cRun Code Cleanup profile on Save\u201d. This will cause the selected profile to be used whenever you explicitly<\/em> save your document. This includes commands like Save, Save All, and the save that occurs when you kick off a build. It will not run Code Cleanup for any automatic saves.<\/p>\n

Keep your files up to date automatically<\/h2>\n

We know many of you love using Ctrl+S to constantly save your documents and that “save often\u201d is an enduring mantra in software development. Visual Studio now enables you to automatically save your dirty documents whenever the Visual Studio application loses focus. When you switch to any other application in Windows, you can have Visual Studio automatically commit your changes to disc for you.<\/p>\n

The autosave feature is still a preview feature and we\u2019re interested in your feedback. We\u2019re considering additional options other than triggering on loss of focus on the Visual Studio window, so let us know what\u2019s working for you and how we can make the experience better.<\/p>\n

To enable the feature today, navigate to Visual Studio Search (Ctrl+Q) and look for \u201cAutosave\u201d. Today, that will take you to the Environment\\Preview Features page in Tools\\Options. Check the option for \u201cAutosave\u201d and Visual Studio will save all dirty documents whenever it loses focus.<\/p>\n

For those of you trying out the Code Cleanup on Save feature we introduced in this preview, automatic saves will not<\/em> trigger Code Cleanup.<\/p>\n

Be more productive with .NET<\/h2>\n

Explore more code with navigate to source<\/h3>\n

We now surface embedded source and Source Link<\/a> as part of Go to Definition if a referenced assembly has embedded source or Source Link. This allows you to navigate to the original source files that declare the target symbol. Place your cursor on a symbol and press F12 to navigate to the original source file.<\/p>\n

\"Moving<\/p>\n

Gain more insight with Stack Trace Explorer<\/h3>\n

A 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 > Other Windows and select Stack Trace Explorer.<\/p>\n

\"Moving<\/p>\n

Enforce consistent naming styles in your code<\/h3>\n

In Visual Studio 2019 we introduced a new UI for 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.<\/p>\n

In this release we added Naming Styles to the EditorConfig UI. With the addition of Naming Styles, you can enforce naming conventions in your code. For example, you could enforce that all interfaces start with the letter \u201cI\u201d. In order to add an EditorConfig file to a project or solution:<\/p>\n