PreviewLogo Visual Studio 2022 version 17.1 Preview Release Notes


Tip

Watch the recordings of the Visual Studio 2022 launch event to learn about what's new, hear tips & tricks, and download free digital swag.

Developer Community | Visual Studio 2022 Roadmap | System Requirements | Compatibility | Distributable Code | License Terms | Blogs | Latest Release Known Issues | Whats New in Visual Studio Docs


Click a button to download the latest version of Visual Studio 2022. For instructions on installing and updating Visual Studio 2022, see Update Visual Studio 2022 to the most recent release. Also, see instructions on how to install offline.

Download Community Button Download Professional Button Download Enterprise Button

Visit the visualstudio.microsoft.com/downloads page to download other Visual Studio 2022 products.

Important

Preview Channel is not "go-live" and not intended for use on production computers or for creating production code. For more information, see Visual Studio Product Lifecycle and Servicing.

Download Community Preview Button Download Professional Preview Button Download Enterprise Preview Button


What's New in Visual Studio 2022 version 17.1 Preview

Visual Studio 2022 version 17.1 Preview Releases

Visual Studio 2022 Blog

The Visual Studio 2022 Blog is the official source of product insight from the Visual Studio Engineering Team. You can find in-depth information about the Visual Studio 2022 releases in the following posts:


17.1.0-pre.4.0 Visual Studio 2022 version 17.1 Preview 4 NewReleaseButton

released January 25, 2022

Issues addressed in this release of 17.1 Preview 4

  • Fixed an issue where sometimes changes to the CMake Workspace settings file would not take effect.

From Developer Community


17.1.0-pre.3.0 Visual Studio 2022 version 17.1 Preview 3 NewReleaseButton

released January 19, 2022

Summary of What's New in this Release of Visual Studio 2022 version 17.1 Preview 3

Web Tools

  • When provisioning and selecting Azure resources Visual Studio remembers the selections you previously made for fields "Resource Group" and "Location" instead of always defaulting to the first entry in the list. Even when a previous selection is not available Visual Studio now calculates the nearest geographical location and picks that by default.
  • Publish profiles are now always listed alphabetically in the drop-down located at the top of the Publish summary page as well as the drop-down in the Visual Studio toolbar called Web One Click Publish.
  • Visual Studio can now generate GitHub Action workflows for Azure Container Apps.

17.1.0-pre.2.0 Visual Studio 2022 version 17.1 Preview 2 NewReleaseButton

released January 5, 2022

Summary of What's New in this Release of Visual Studio 2022 version 17.1 Preview 2

C++

  • A new Configure Preset template has been added to configure and build CMake projects on a remote macOS system with CMakePresets.json. You can also launch CMake targets on a remote macOS system and debug with the front-end of the Visual Studio debugger backed by GDB or LLDB.
  • You can now debug core dumps on a remote MacOS system from Visual Studio with LLDB or GDB.
  • The versions of Clang and LLVM shipped with Visual Studio have been upgraded to v13.
  • Visual Studio's CMake integration will only activate when a CMakeLists.txt is identified at the root of the open workspace. If a CMakeLists.txt is identified at another level of the workspace, then you will be prompted to activate Visual Studio's CMake integration with a notification.
  • Added a new register visualisation window for embedded targets, available through Debug > Windows > Embedded Registers.
  • Added a new thread view for RTOS projects, available through Debug > Windows > RTOS Objects.

Git Tooling

  • Added capability to compare branches in Visual Studio
  • Introduced enhancements to the detached head state including the ability to checkout commits
  • Multi-repo branching enhancements including the ability to create branches accross different repositories at the same time (preview feature)
  • Line-staging support, a.k.a interactive staging with the ability to stage specific lines and/or chunks of code (preview feature)

Editor

  • Visual Studio can now automatically save code documents whenever the application loses focus. This feature is currently a preview feature and can be accessed in Tools\Options under Environment\Preview Features. If the "Autosave" option is checked, Visual Studio will attempt to save all dirty code documents whenever the Visual Studio application loses focus (e.g. when switching to another application in Windows).
  • The Code Cleanup feature can now be configured to be run whenever a file is explicitly saved. In Tools\Options under Text Editor\Code Cleanup, a new option allows users to enable the Code Cleanup on explicit save as well as to select the profile to run. Note that this option will not cause Code Cleanup to be run on autosave.

IDE

  • Add your Github AE account using the integrated account management experience (Requires enabling GitHub Enterprise Server accounts)
  • Added ability to toggle color scheme to color your tabs by File Extension or Project.
  • Added capability to customize tab colors when color tabs are enabled. Right-click on a color tab and select Set tab color.

Razor (ASP.NET Core) Editor

  • Razor will now add missing using directives if a quick action requires one.

.NET Productivity

  • We now surface Source Link as part of Go to Definition, allowing you to navigate to the original source file.
  • We added a new Stack Trace Explorer window.
  • The EditorConfig UI now includes Naming Styles.

Test tools

  • Code coverage tools can now produce the cobertura code coverage format. You can enable this in runsettings by adding <Format>Cobertura</Format> in the DataCollector configuration section in your runsettings file. This format can be viewed in the code coverage results window in Visual Studio Enterprise.
  • You can also collect with the cobertura format from the cli by either specifying it in the runsettings file or specifying it in a parameter. For the dotnet cli use dotnet test --collect:"Code Coverage;Format=Cobertura". For vstest use vstest.console.exe /collect:"Code Coverage;Format=Cobertura". The collect parameter will override the format specified in runsettings.

Microsoft Teams developer tools

  • Added Microsoft Teams development tools as an optional component during installation of the ASP.NET web development workload.
  • Installing this component adds the Teams Toolkit extension. Use the new Microsoft Teams App project template to get started.

Issues addressed in this release of 17.1 Preview 2

From Developer Community

Details of What's New in this Release of Visual Studio 2022 version 17.1 Preview 2

.NET Productivity

  • We now surface embedded source and Source Link 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.

Source Link Navigation

  • There is now a Stack Trace Explorer Window that displays stack traces from the clipboard allowing you to click and navigate directly to the related code. By default, if you copy a stack trace from your solution and then switch focus to the Stack Trace Explorer window, the stack trace will automatically appear. To open the Stack Trace Explorer window, go to View > Other Windows and select Stack Trace Explorer.

Stack Trace Explorer window

  • In Visual Studio 2019 we introduced a new UI for EditorConfig. 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. In this release we added Naming Styles to the EditorConfig UI. To add an EditorConfig file to a project or solution, right click on the project or solution name within the Solution Explorer. Select Add New Item. In the Add New Item dialog search for EditorConfig. Select the .NET EditorConfig template to add an EditorConfig file prepopulated with default options. Notice the new EditorConfig UI and the new Naming Styles option.

EditorConfig Naming Styles

Microsoft Teams developer tools

Teams Toolkit is a Visual Studio Extension to help developers create experiences for Microsoft Teams and is part of the Microsoft Teams Framework (TeamsFx). Learn more about Teams Toolkit and TeamsFx on GitHub and in the Microsoft Teams documentation.

  • Choose the Microsoft Teams development tools component in the ASP.NET web development workload in the Visual Studio Installer.
  • Create a new project and select the Microsoft Teams App project template to begin with creating a new Teams tab application.

Thank You

Last but certainly not least, a big Thank You to the following people who contributed this month to .NET Productivity (a.k.a. Roslyn):


17.1.0-pre.1.0 Visual Studio 2022 version 17.1 Preview 1.1

released November 16, 2021

Issues addressed in this release of 17.1 Preview 1.1

  • Under some circumstances the publish of a worker service to an Azure Container Apps would silently fail.
  • Fixed an issue where Visual Studio failed to start on Windows 7 machines.

17.1.0-pre.1.0 Visual Studio 2022 version 17.1 Preview 1

released November 08, 2021

Summary of What's New in this Release of Visual Studio 2022 version 17.1 Preview 1

Debugging & Diagnostics

  • Added a support for Microsoft Azure App Services Attach to Process.

Git Tooling

.NET Multi-platform App UI (MAUI) Preview 10

  • .NET MAUI Preview 10 is now available.

.NET Productivity

  • Go To Definition from source information in PDBs.
  • IntelliSense completion for await within an awaitable expression.
  • Move static members to a new type refactoring.
  • Simplify code to use the new C# 10.0 extended property patterns refactoring.
  • Detect variable swaps and suggest using a tuple to swap values refactoring.
  • Code definition window support for C# and Visual Basic.
  • Enable nullable reference types across a project refactoring.
  • Signature help simplified view improvements when a tuple appears many times within a signature.
  • Understand errors and warnings at a glance with inline diagnostics.

XAML Hot Reload

  • XAML Hot Reload now supports more end-to-end scenarios when using together with .NET Hot Reload.

XAML Live Preview

  • XAML Live Preview now supports .NET MAUI apps (WinUI & Android).

Top Voted Issues From Developer Community

Please see our full list of Developer Community fixes in this release.

Known Issues in 17.1 Preview 1

Details of What's New in this Release of Visual Studio 2022 version 17.1 Preview 1

Debugging & Diagnostics

Microsoft Azure App Services Attach to Process

You can now attach to your .NET (Framework. Core, or 5+) for Windows App Service without a solution or project open.

Open the Attach to Process Dialog -> Change the Connection Type to Microsoft Azure App Services -> Select Find -> Select your Subscription and then find your App Service under the resource group and hit “Ok�. Find the process you want to connect to and select “Attach�.

.NET Multi-platform App UI (MAUI) Preview 10

  • In this release you can use Visual Studio 2022 to create a new or continue to work on an existing .NET MAUI application.
  • .NET MAUI also supports features such as XAML Live Preview (for WinUI and Android Emulator) and .NET Hot Reload for all platforms.

For more details on our Preview 10 release please see the .NET Blog.

.NET Productivity

  • When building managed libraries developers can choose to embed their source files with the debug information (PDB file) that is produced by the build, and even embed the PDB file into the assembly itself. We now surface embedded source as part of Go to Definition if a referenced assembly has embedded source and the PDB is available. 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.

  • There is now 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.

  • There is now a refactoring to move static members to a new type. Place your cursor on a static member. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Move static members to another type.... This will open a dialog where you can select the members that you would like to move.

    Move static members to another type refactoring

  • There is now a refactoring to simplify code to use the new C# 10.0 extended property patterns. Using extended property patterns reduces noise allowing you to reference nested members instead of nesting another recursive pattern. Place your cursor on a nested member reference. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Simplify property pattern.

    Simplify property pattern refactoring

  • There is now a refactoring that detects variable swaps and suggests using a tuple to swap values so instead of using a temporary variable in-order to swap arguments you can use a tuple. Place your cursor on a temporary variable assignment where you are swapping values. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Use tuple to swap values.

    Use tuple to swap values refactoring

  • The Code Definition Window now supports C# and Visual Basic. To use the Code Definition Window, either press (Ctrl+W,D) or select View > Code Definition Window. Next, place your cursor on an identifier to navigate and explore code.

    C# and Visual Basic support in the Code Definition Window

  • There is now a refactoring to enable nullable reference types across a project. You can enable nullable reference types by adding the <Nullable>enable</Nullable> element to your project file or add the #nullable enable pragma to every source file in your project. To help streamline this process we now automatically include the <Nullable>enable</Nullable> for new .NET projects. For existing .NET projects, you can enable nullable reference types by placing your cursor on a #nullable enable pragma. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Enable nullable reference types in a project.

    Enable nullable references types across a project refactoring

  • Signature Help has improved its display when a tuple appears many times within a signature. The simplified view includes the Structural Type key to show you what is contained in the tuple.

  • You can now understand errors and warnings at a glance without needing to hover your cursor over a line of code with Inline Diagnostics. Inline Diagnostics is disabled by default so you will need to enable it in Tools > Options > Text Editor > C# or Basic > Advanced and select Display diagnostics inline (experimental).

    Inline Diagnostics

XAML Hot Reload

In this release we continue to preview our on going work to create a better experience when using both XAML and .NET Hot Reload together.

In this release we’ve enabled the following scenarios:

For WPF and WinUI 3 apps:

  • XAML code editor will now properly show newly created control types and properties created by a .NET Hot Reload operation in IntelliSense
  • Binding to a newly created property using .NET Hot Reload will now work as expected. For WinUI you can also now use x:Bind to bind to a new property as well

For WPF apps:

  • Adding a newly created method for an event handler created using .NET Hot Reload will now work

To help us test these new features, make sure you turn on the preview flag under “Options > Preview Features > XAML IntelliSense updates after .NET Hot Reload”.

Note: While the above scenarios work if the types are first applied using .NET Hot Reload and then XAML Hot Reload is used, there is a known limitation. For example, if you add assign a new property using XAML Hot Reload to a property that has not yet been created and only then use .NET Hot Reload to create it, the XAML change will not see the new property. We are aware of this issue and hope to improve it in the future.

XAML Live Preview

  • In this release XAML Live Preview is supported for .NET MAUI apps running as either a WinUI 3 app or in an Android Emulator

Known Issues

See all open issues and available workarounds in Visual Studio 2022 by following the below link.


Feedback and suggestions

We would love to hear from you! You can Report a Problem or Suggest a Feature Feedback Icon by using the Send Feedback icon in the upper right-hand corner of either the installer or the Visual Studio IDE, or from Help > Send Feedback. You can track your issues by using Visual Studio Developer Community, where you add comments or find solutions. You can also get free installation help through our Live Chat support.


Blogs

Take advantage of the insights and recommendations available in the Developer Tools Blogs site to keep you up-to-date on all new releases and include deep dive posts on a broad range of features.


Top of Page