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

  • Philipp Gilbert Baumgartner

    I find the mentioned changes all good and useful.

    But I would be happy if VS also had the option of upgrading from VS 2019 to VS 2022 and not just having the option of reinstalling the new generation. In my opinion, when VS 2022 is officially available, the installer should receive an update (no reinstallation of the installer for VS 2022), with which VS 2022 is added to the overview of all editions. In addition, in the overview of the installed version, there should be an upgrade option from VS 2019 to VS 2022 without just reinstalling VS 2022. If you want both versions, you can install VS 2022, but if you only want VS 2022, you don’t have to install VS 2022 and uninstall VS 2019, because people can use the upgrade option to upgrade from VS 2019 to VS 2022.

  • Ayush Gupta

    So, the IDE is not getting fluent design system elements? Whether it be icons or other elements of the IDE on windows but the IDE is getting the native elements on macOS? Why? 🙄

  • Jeff Jones

    I applaud the new features, the support for .NET 6, MAUI, etc.

    However, if there is no visual designer for Xamarin Forms/MAUI, then your team failed. Big.

    The productivity gain in having a visual designer is immense. That is why Visual Studio (preceded by the Visual Basic IDE) has had one for over 25 years. And don’t give me the silly argument “it is too hard to do”. Alan Cooper and his small team built the “mother of all visual designers” in C++ for VB when it first came out.

    By failing to build an efficient, usable, visual designer, MS is admitting that they can’t even accomplish something a small team did back in the 90s.

    Either hire the right team to build this, or keep losing market share to the IDEs that the other “command line kiddies” like.

    • Stevie White

      Even though I primarily do most of my work using markup (HTML or XAML) these days, I can’t help but agree. Having a designer is an immense time saver, even if you just need to see a preview in the IDE of what you are coding up instead of having to waste time building or dealing with the nuances of hot reload (let’s face it, Hot Reload is nice but it doesn’t always work and sometimes you have to recompile in order to see the full extent of your changes).

      It is befuddling especially since the word “VISUAL” is in the name of Visual Studio, implying that you can see what you are making. I know it’s just a word, but to me not having some sort of designer for the modern frameworks (MAUI, Blazor and/or whatever truly succeeds WPF) is bizarre when this is the IDE that came from a line of successful application environments that were heavily designer oriented.

      Edit: Just to also note – I got my start using Windows Forms and I can say that while I still prefer WPF for the desktop development story, there were a LOT of things that the Windows Forms designer did MUCH better than WPF’s. WPF’s designer feels more like a live preview than a real designer due to its nasty habit of polluting your xaml files with garbage markup).

    • Kevin Weir

      I agree completely. To me this is one of the primary reasons why desktop development stagnated the last few years. Had Microsoft released a world class WYSIWYG editor for XMAL years ago, the desktop application portfolio would be much more substantial and healthier today. I believe that to be the case anyway.

    • Eric Lynch

      I also agree. The original WinForm designer was groundbreaking. All the designers since have sucked! Leave it to MS to create something revolutionary…then, instead of evolving it to be even better, spend a couple of decades moving in the wrong direction.

      I’m similarly disappointed by all the Dotnet, NuGet, EF, and other command-line crap that keeps creeping into “Visual” studio. I find myself constantly switching back and forth between visual design, markup (like XAML), and this command-line nonsense that belongs back in the pre-PC days. It’s a wildly inconsistent experience and negatively impacts my productivity.

    • hitesh davey

      A WinForms like pixel-perfect WYSIWYG designer is required for Core, Blazor, Xamarin Forms/MAUI. That will accelerate new app development in the real sense. otherwise, many developers may opt 3rd party Tools (e.g. WISEJ ) & IDEs for rapid application development. I hope MS is reading the user’s voice i.e concerns.

  • Sonu Lohani

    Any news for linux operating system… I want to run vs 2022 in ubuntu

    • Jorge Morales Vidal

      You can run Visual Studio Code on Linux, you can develop .NET 5/.NET 6 applications with the .NET SDK and the VS Code C# extension.

  • Jean Ressouche

    – Great for 64-bit & other imrpovements!
    – Indeed, i don’t get the icons part, it’s nothing exciting, they are not better (some are really worst)
    – Is Xamarin endanger / will die like Silverlight did because of MAUI?
    – Agree with many comments: Azure DevOps (specially Server version) continuation & improvement (itself + integration with VS) should resurrect in MS RoadMap!

  • TSX

    Adding 64 bit is good, but there are more important needs:

    – uniform zoom for whole IDE (menu, tool’s windows, tooltips, editor). Right now there is inconsistent experience where editor content is zoomed, while all other is tiny. This creates serious readability problems, especially on YouTube vids, where that tiny text / images are often fuzzy

    – differential compiling / linking / optimizing. Compiler should track changes in files, and reduce amount of work / time to create build. Currently after make change to single file (out of many), all files are compiled, which is often very slowly. There is huge potential to shave 99% of build times. This is similar to Hot Reload, but for compiling.

    – with 64 bit, there is possibility to move extensions into main process, and eliminate inter-process communication. This will simplify writing extensions and increase speed. For make this happen you must create some ‘in process sandbox’, where VS will track all resources (memory, threads, files and others) used by extension, and clear it when extension crash.

    – do not mess with icons and other UI elements with every release. Make VS customizable, so every can use icons he like and create / modify menu.

    – too slow nuget UI tool – need 10 sec to appear

    • Dante GagneMicrosoft employee

      I’d love to understand a bit more about the Uniform Zoom statement you made. We’ve held a hypothesis that folks who want to scale the entire UI would do so with OS settings. In general, changing the values in the Display Settings to apply a uniform scaling to everything.

      Personally, my vision isn’t what it used to be, but I’ve found that I just set an overall scaling to Windows all-up and all my applications get scaled uniformly. It sounds like that issue doesn’t work for you and I’d love to get a sense of the scenarios that are getting in your way.

      • TSX

        uniform zoom can be done on two ways. Both ways are availabe in Windows, but can be integrated into VS to get better results:

        – DPI at application level. While global DPI can be changed, but this is tedious and distracting. There should be combination of keys (defined in tools -> options) to do it quick, without leaving VS, and apply only to VS. There could be defined step in tools -> options (like 10%), which is applied when user change DPI level.

        – virtual screen. When VS run in full screen mode, then user can artifically decrease size of screen (using keys), so only part of VS will be visible, but this part will be magnified. Then user can move his view using mouse moves. Center of view could be insensitive for mouse moves, and do not cause view’s moving, but moving cursor on border (thickness defined in options), will cause that view is moving (VS is scrolling in one direction). This is similar to system application Magnifier, but will work without running Magnifier. Switching from VS to other app cause return from view, and switching back to VS, will bring view back, at position when VS was before switch.

        User can use these two ways simultaneously.

        hopefully it is compilable 🙂

        • Dante GagneMicrosoft employee

          It makes sense… and I was chatting with the Program Manager who headed up the process to get Visual Studio to handle different DPIs at the same time about this. The argument against doing what you’re suggesting is that since Visual Studio has so many different UI frameworks, it was a really tricky operation to get “Per Monitor-DPI” to work correctly. To add another scaling factor on top of that has a complexity that we weren’t sure we wanted to tackle.

          When we analyzed the use cases, it was pointed out that you can set the DPI/Scaling in Windows for an all-up experience or you can use a tool like Magnifier for something like the Virtual Screen experience you described above. Since those already existed, it seemed like there were other features that would provide more value as opposed to integration with existing tools.

          I won’t disagree with that there’s value in an integrated experience… but I’m inclined to focus on other features. Make sense?

  • Max Mustermueller

    Devs: Please give us 64bit
    MS: Nah, not necessary
    Devs: Please give us 64bit
    MS: Nah, not required
    Devs: Please give us 64bit
    MS: Nah, too complicated
    … 10 years later
    MS Employee: Hey bro, I got a really cool idea. Lets make a 64bit VS.
    MS Rest of team: Oh, that sounds useful. Okay lets do it.

  • John King

    I agree @leoniDEV , and the new Git experience is terrible in “Git Changes” window !!!
    I like “Team Explorer”‘s Git experience, and yes , there are many new feature in the new Git UX, but all of them can be done in “Team Explorer” too, but MS just goes to “Git Changes” which it’s just one tab in the “Team Explorer” .

    and the MAUI, I can sure that this MAUI dead in China already , even it isn’t born yet. Why ? because:
    1. do not cross Windows platform (cut Windows 7 )
    2. limited Android Platform (TV’s still using Android 4 or Android 5)
    3. for MacOs and Iphone , I’m not very sure.

    Why a company use such a new tech that support less platform than UniApp or Election or Flutter ?( Note: if a new UI stack do not support WeChat’s mini program , then it’s already losing 35% market in China at least , but if dotnet foundation can also bring MAUI or some UI tech to WASM, and one day that mini program support WASM, then .net can rob 10% market in just 1 year, because that also enable Unity3d, Striped , WawEngine to mini programe too, and this will hep .net ecosystem too)

    And a Question: Why Visual Studio still using .net framework instead of .net 5/6 after 5 years later that .net core born ?
    I mean with .net 5/6 , you get cross platform , Vs For windows and Vs for Mac became 1 product, and also available in Html via Web Assembly .

  • Himanshu Shekhar

    It’ll be great if VS 2022 IDE has complete JAVA development workflow. Now more so, when MS is distributing its own Open JDK build. This will remove burden of having two IDE’s where other one is exclusively for JAVA.

    • kuzbas123

      totally. you never want a bunch of excess software on your computer.

  • Andrei Nosatîi

    The most important thing is robust support for the C++ 👌

    • Dominique Gratpain

      Why not, if you like C++.
      Me, I prefer VB and I want the same functionnalities and robust support for every language.
      Everybody must find happyness with Visual Studio.