Visual Studio 2022


Visual Studio 2022 launch is here!

Join us at our free online event to celebrate the launch of Visual Studio 2022. Learn about what’s new, hear tips & tricks, participate in the live Q&As, and be the first to take the latest version for a spin.


All of our product development begins and ends with you—whether you posted on Developer Community, filled out a survey, sent us feedback, or took part in a customer study, thank you for helping to continue to steer the product roadmap for Visual Studio. I have exciting news—the first public preview of Visual Studio 2022 will be released this summer.

The next major release of Visual Studio will be faster, more approachable, and more lightweight, designed for both learners and those building industrial scale solutions. For the first time ever, Visual Studio will be 64-bit. The user experience will feel cleaner, intelligent, and action oriented.

Development teams have become more geographically dispersed than ever. It’s become apparent over the last year that organizations need their development teams to collaborate securely, deliver solutions more quickly, and continuously improve their end-user satisfaction and value. We’re making it easier to collaborate with better GitHub integration making it seamless to go from idea to code to the cloud.

Visual Studio 2022 is 64-bit

Visual Studio 2022 will be a 64-bit application, no longer limited to ~4gb of memory in the main devenv.exe process. With a 64-bit Visual Studio on Windows, you can open, edit, run, and debug even the biggest and most complex solutions without running out of memory.

While Visual Studio is going 64-bit, this doesn’t change the types or bitness of the applications you build with Visual Studio. Visual Studio will continue to be a great tool for building 32-bit apps.

I find it really satisfying to watch this video of Visual Studio scaling up to use the additional memory that’s available to a 64-bit process as it opens a solution with 1,600 projects and ~300k files. Here’s to no more out-of-memory exceptions. 🎉

64-bit VS opening 1600 projects

We’re also working on making every part of your workflow faster and more efficient, from loading solutions to F5 debugging.

Designing for everyone

We’re refreshing the user interface to better keep you in your flow. Some of the changes are subtle cosmetic touches that modernize the UI or reduce crowding. Overall, we aim to reduce complexity and decrease the cognitive load so that you can focus and stay in the zone. Also, making Visual Studio more accessible delivers better usability for everyone – the next version of Visual Studio will include:

  • Updated icons for better clarity, legibility, and contrast.
  • Cascadia Code, a new fixed-width font for better readability and ligature support. (If you like, you can try Cascadia Code today!
  • Refreshed and improved product themes.
  • Integration with Accessibility Insights to detect accessibility issues early on—before they get to your end-users.

Visual Studio 2022 icon refresh


Developer to developer, we understand that personalizing your IDE is as important as picking your desk chair. We have to make it “just right” before we can be at our most productive. It will be easier than ever to make Visual Studio 2022 “just right” for you, from the ability to customize aspects of the IDE to syncing settings across devices for those who maintain multiple dev boxes.

Developing modern apps


Visual Studio 2022 will make it quick and easy to build modern, cloud-based applications with Azure. We’ll get you started with a good supply of repositories that describe common patterns used in today’s apps. These repositories are made up of opinionated code showing these patterns in action, infrastructure-as-code assets to provision the Azure resources, and pre-built GitHub workflows and actions setting you up with a complete CI/CD solution when you first create a project. Plus, the required development environment will be defined in the repository so that you can start coding and debugging right away.


Visual Studio 2022 will have full support for .NET 6 and its unified framework for web, client, and mobile apps for both Windows and Mac developers. That includes the .NET Multi-platform App UI (.NET MAUI) for cross-platform client apps on Windows, Android, macOS, and iOS. You can also use ASP.NET Blazor web technologies to write desktop apps via .NET MAUI.

.NET MAUI app types

And for most app types like web, desktop, and mobile, you’ll be able to use .NET Hot Reload to apply code changes without needing to restart or lose the app state.

.NET Hot Reload in action


Visual Studio 2022 will include robust support for the C++ workload with new productivity features, C++20 tooling, and IntelliSense. New C++20 language features will simplify managing large codebases and improved diagnostics will make the tough problems easier to debug with templates and concepts.

We’re also integrating support for CMake, Linux, and WSL to make it easier for you to create, edit, build, and debug cross-platform apps. If you want to upgrade to Visual Studio 2022 but are worried about compatibility, binary compatibility with the C++ runtime will make it painless.

Innovation at your fingertips

Diagnostics and debugging

The ability to confidently debug your applications is at the center of your daily workflow. Visual Studio 2022 will include performance improvements in the core debugger, with additional features like flame charts in the profiler for better spotting the hot paths, dependent breakpoints for more precise debugging, and integrated decompilation experiences which will allow you to step through code you don’t have locally.

Real-time collaboration

Live Share opens new opportunities for collaborating with others, exchanging ideas, pair programming, and reviewing code. In Visual Studio 2022, Live Share will introduce integrated text chat so that you can have quick conversations about your code without any context switches. You’ll have options to schedule recurring sessions that reuse the same link, simplifying collaboration with your frequent contacts. To better support Live Share within organizations, we’ll also introduce session polices, that define any compliance requirements for collaboration (e.g. should read/write terminals be shareable?).

Insights and productivity

The AI IntelliCode engine in Visual Studio continues to get better at seamlessly anticipating your next move. Visual Studio 2022 will provide more and deeper integrations into your daily workflows, helping you to take the right action in the right place at the right time.

Whole word completion

Asynchronous collaboration

Visual Studio 2022 will include powerful new support for Git and GitHub. Committing code, sending pull requests, and merging branches is when “my code becomes our code.” You’ll notice a lot of built-in logic and checkpoints to guide you efficiently through the merge and review process, anticipating feedback from your colleagues that could slow things down. Our guiding principle here was helping you to have higher confidence in the code you deliver.

Code search is an integral part of the software development lifecycle. Developers use code search for lots of reasons: learning from others, sharing code, assessing the impact of changes while refactoring, investigating issues, or reviewing changes. We’re committed to delivering better performance for all these critical activities in Visual Studio 2022 to make you even more productive. You will also be able to search outside your loaded scope, to find what you’re looking for no matter what code base or repo it’s located in.

Refreshing Visual Studio for Mac

Our goal with Visual Studio 2022 for Mac is to make a modern .NET IDE tailored for the Mac that delivers the productive experience you’ve come to love in Visual Studio. We’re working to move Visual Studio for Mac to native macOS UI, which means it will come with better performance and reliability. It also means that Visual Studio for Mac can take full advantage of all the built-in macOS accessibility features. We’re updating the menus and terminology across the IDE to make Visual Studio more consistent between Mac and Windows. The new Git experience from Visual Studio will also be coming to Visual Studio for Mac, beginning with the introduction of the Git Changes tool window.

Let us know what you think!

We’ve only shown you a few highlights of our work in progress, but we welcome your initial thoughts on the direction we’re taking for Visual Studio 2022. As always, you can head on over to the new Developer Community to browse through existing feature requests to upvote and comment or create your own.

Stay tuned for announcements about the 64-bit Visual Studio 2022 Preview 1 availability, which will include our UI refinements and accessibility improvements. (And remember! Like any work in progress, these features are still in development, so some of them will be coming to Visual Studio 2022 after the first public release.)

Thank you!


Editor’s Note: The post was originally published on 4/4/21 and was updated on 7/16/21 to add a note that Visual Studio 2022 Preview has been released.


Comments are closed. Login to edit/delete your existing comments

  • Christian Bobsin

    Windows Version , Mac Version…

    And the Linux Version?

    Visual Studio 2025 maybe? 🙂

  • Dominique Gratpain

    Don’t forget ReportViewer (RDLC reports) with WinForms.
    I always saw with all news versions many issues with ReportViewer.

    • Daniel Smith

      The fact that the RDLC report viewer controls haven’t been ported to .NET Core is a major blocker for migrating for most of the apps I work on. They’re trying to push PowerBI as an alternative, but it’s absolutely useless in an offline desktop scenario. Plus there are no UI controls for hosting PowerBI reports in WinForms or WPF. With the SSRS RDLC report libraries and controls, you can generate and preview a report client side. I absolutely can’t tell the users of my offline desktop apps who want to print a piece of stationery (e.g. a delivery note or a safety certificate) that they have to buy and install a local Power BI server!

      Support for SSRS reports in .NET Core is currently the 4th highest voted request on the SQL Server feedback site (the team that own the .NET controls), but unfortunately they’ve not responded to it in over 3 years! Is there any product manager that could chase the SQL Server team for a response? Here’s the suggestion which currently has 1,150 votes:

  • Björn Holmgren

    Sounds great, so far! 🙂

    Will be fun take a look at the new UI, .Net 6, intellisense, and git support.


  • Mike Christensen

    Honestly none of these new features mean anything until you manage to make Visual Studio faster. I switched to Rider a while back simply because Visual Studio is too slow to be useful as an IDE. I’ll definitely try out Visual Studio 2022 when it’s available, but unless huge leaps and bounds have been made in terms of responsiveness, I’ll probably pass.

  • Jason Stone

    This can’t arrive soon enough. Half my co-workers are switching to JetBrains Rider because it already has a lot of these features, a better designed UI and is more performant.

  • Zehev Spitz

    Is there any hope for improving custom debugging visualizers?

    The discovery and deployment story is abysmal. Currently, info about visualizers is spread via word-of-mouth (no Visual Studio Marketplace); installation is either a custom installer, or a copy-paste to one of two folders while keeping the folder structure needed for targeting frameworks/bit-nesses that differ from VS; and there’s no update notification mechanism. There’s also no built-in mechanism allowing for dependent DLLs, which means the developer has to write their own such mechanism, or include everything and the kitchen sink in the single DLL, or risk overwriting different versions of dependent DLLs.

    The visualizer API offers no information beyond the value/object being targeted (e.g. the expression being targeted, the source file and line number, the language of the expression, the current assembly); and sometimes not even that (

    Even though these visualizers are intended to be used with Visual Studio, there is no defined way to visually integrate them with VS themes and controls.

    The requests I’ve filed on Developer Community about these issues have either been closed, or aged away. (I’ve compiled a list.)

    As the author of 3 visualizers (and counting) — for expression trees, ANTLR4 parse trees, and DateTime — I urge you to consider updating the development story, to be at least on par with other VS extensions.

  • Ian Marteens

    I prefer FiraCode Light to Cascadia but, sure, it’s a matter of taste.

    • Dante GagneMicrosoft employee

      What, in your opinion, does FiraCode do better than Cascadia? I used FiraCode myself for a while until I got told about Cascadia. I’m curious what makes one better than another?

      • Yann Duran

        I’ve used Fira Code for a while now. I wanted to try out Cascadia Code, but switched immediately back to Fira Code as it was much clearer and easier for me to read.

  • Rod Macdonald

    Blazor + HTML/CSS to one side, my biggest concerns are: 1) there doesn’t appear to be a common, cross-platform UI stack to take on Flutter e.g. WinUI does not ‘out of the box’ run in the browser. Many months ago I asked the XAML team to consider creating the XAML stack either as an extension to HTML, making it parallel to HTML or even replacing HTML and XAML with something like SVG; 2) that not parking up WinForms (which I love by the way) and WPF with .NET 5 is slowing down your agility – again to allow you to develop a cross-platform UI stack like Flutter.

    Blazor to the forefront: 3) as commented elsewhere in this column, design support for HTML/CSS and XAML (or any successor) is paramount. I think the Radzen model is beginning to shine in this way, if only something like this were baked into VS. It’s super hard to design responsive elements in CSS without a visualiser for things like FlexBox and CSS Grid.

    MS are historically very adept at using there own technology in the applications they build. VS2022 should be no exception.

  • Rick Moore

    Does the move to 64-bit also apply to SQL Server Integration Services projects or Data Tools?