Visual Studio 2022 now available

Amanda Silver

Watch the Visual Studio 2022 keynote

Our launch event is over. In case you missed it, you can watch the keynote on YouTube.

I am really excited to announce that we’ve reached general availability for Visual Studio 2022 and .NET 6, both of which are now available for download. Visual Studio 2022 will help you go from idea to code faster than ever. Developer productivity and quality-of-life improvements are at the heart of Visual Studio 2022, and we’re excited for you to try it out. Simply put, Visual Studio 2022 will let you bring your ideas to life.


Productivity in the edit and debug cycle

In this release, we focused on super-charging the edit and debug cycle.

Visual Studio 2022 has IntelliCode. It’s an AI-assisted code companion that enables you to type less and code more. What this means is IntelliCode can now complete whole lines of code for you, allowing you to write dependable code in just two taps of the tab key. IntelliCode can also spot repeated edits and suggest fixes throughout your codebase where there are similar patterns.

Once you’ve made those changes and have your app running, Hot Reload for .NET and C++ gives you the opportunity to update your code and see changes immediately. What’s more, you won’t need to redeploy and launch your application. And there are hundreds of other things under the hood that will help you. Some of the others include improvements in the debugger and .NET language service as well as new features, like Web Live Preview and cross-platform testing on Linux. There are so many new capabilities and fixes that we just can’t list them here, but we have in our release notes and documentation.

Visual Studio 2022 is the IDE for you. It’s for every developer, from apps built with Windows Forms and Win32, to Blazor, to cloud-native applications based on containers, to applications that use machine learning.

Scalability, reliability, and performance

Visual Studio 2022 is our first 64-bit release of Visual Studio. It can now take full advantage of modern hardware in order to reliably scale to larger, more complex projects. In addition, we’ve focused on improving the performance of common scenarios that you use every day.

Tune in and watch our launch event

Don’t forget to check out our Visual Studio 2022 launch event. It’s today at 8:30 a.m. Pacific. You can catch it live on or our Twitch channel. And it’ll be available on our YouTube channel later on, in case you can’t watch it live.

Scott Hanselman will kick things off by interviewing our product team. The product team will show off what Visual Studio 2022 can do. After that, 10 demo-driven “What’s new” sessions – just 20 minutes each and aimed at specific application platforms – will continue getting you up to speed with what’s in Visual Studio 2022. Want tips and tricks? You’re in luck. We have 30 sessions to help you out. And to cap things off, we’ll have a live Q&A with the product team. If you want to get in on the action, you can ask questions throughout the day via the integrated Q&A chat application.

If you want to get in on the festivities, use the hashtag #VS2022 on Twitter during the event. To learn more about the event, check out this blog post.

Watch the .NET Conf 2021

On November 9, you can watch the .NET Conf 2021. It’s three days of packed content from Microsoft and Microsoft community. We have sessions on everything from the latest C# language features, modern cloud, web and native device development, and 80 live sessions on topics covering everything you need to know about .NET. Tune in and feel free to ask questions live on Twitter using #dotNETConf.

What’s next?

Today, we’re also shipping the first preview of the first update to Visual Studio 2022, 17.1. You can find it on the Visual Studio 2022 Preview channel. And keep your eyes peeled in the future for regular updates that will add fixes and new features. If you want to read about our release cycle, make sure to read this. But what will we actually include in the releases? We have you covered. Look no further than the Visual Studio 2022 Roadmap.

Thank you


We couldn’t have made this happen without you. We’ve received an incredible amount of feedback from the thousands upon thousands of developers who have tried the previews. You have all provided so much feedback, from survey responses to bug reports, all of which helped shape the direction of Visual Studio 2022. Including over a thousand fixes to bugs reported by our community. Truly, we want to thank everyone.

We’re not done hearing from you, though. Far from it. Give us feedback as you use Visual Studio 2022. After all, that’s how we’re going to continue to make Visual Studio 2022 as good as it can be.

We also want to thank our extension partners who have been with us on this journey to 64-bit. Thanks to their hard work, over 500 extensions for Visual Studio 2022 are available today from the Marketplace.

Happy coding!


Discussion is closed. Login to edit/delete existing comments.

  • Prem Shah 0

    Is there any easy way to manage version number and build number to multiple (200+) projects in single solution?
    Is there a easy way to auto increment build number in multiple (200+) projects in single solution ?

    • Miha Markic 0

      Why not use a build process to manage that for you? Like MSBuild or Cake.

    • Michael Taylor 0

      Script it. But I’m not sure what you mean by build number as your solutions probably aren’t referencing a specific build of anything that you’d want to auto-update to. If you wanted to, for example, update to .NET 6 then presumably you’d test the projects as you went along first. If you updated all of them to .NET 6 and then something failed you wouldn’t know what broke it. But if you did want to update all your solutions/projects at once then a simple grep tool like Powershell would work.

    • Mark DownieMicrosoft employee 0

      Hi Prem,

      Not necessarily from within Visual Studio, however, most developers tend to script this kind of version increment action via the build or CI/CD process.


    • Vishal Bhatt 0

      One way is to use the GlobalAssembly file and add that as a link to all your projects in the solution. This way you just need to define the version and build number in one file and all your projects in the solution take those numbers.

  • Øystein Heimstad 0

    And the Return code: -2147024690 error is still not fixed. A lot of people have reported this problem but nothing is done.
    So you can’t install VS 2022 anywhere you want.

      • Alfred J 0

        How do you upgrade VS 2019 community to VS 2022?
        VS2019 community doesn’t upgrade thru the VS programs auto or manual update and when i try to download the VS 2022 community from the link to reinstall, as it is 64bit, and it is the same download as the 2019 from October 2021.

  • Hristo Hristov 0

    After updating from 2022 RC to 2022 all shortcuts but the main remained postfixed with an “RC”. This is quite annoying.

    • Michael Taylor 0

      This has always been a problem. I don’t think it is a VS-specific issue but rather a Windows Shell caching issue as the IDs haven’t changed so the shell doesn’t properly update. I’ve seen it on other apps as well such as the Windows SDK and Powershell.

      • Hristo Hristov 0

        You are right. I remember now that it has happened before. I don’t remember how I have had it fixed. One would expect that this would have been fixed after so many years.

        Maybe they shouldn’t have added the RC to the shortcuts and saved us the trouble.

        • Anthony CangialosiMicrosoft employee 0

          You can manually rename the Start menu item to “Visual Studio 2022”. This won’t have any negative affect on VS. Please do log a feedback ticket though.

    • Alexey Gritsenko 0

      My shortcut renamed to “Visual Studio 2022 Current” automatically

  • Piotr Karczmarz 0

    Congratulations to entire team! The next 64-bit Visual Studio era begins!

    • Anthony CangialosiMicrosoft employee 0


    • Mark DownieMicrosoft employee 0

      Thanks for the feedback Mike, you referenced a feedback ticket that will get routed to the appropriate internal team to check out this issue. Thanks for you patience.


    • Fabien Geraud 0

      If they are not to busy to find a way to remove it from the cli silently. They may found time to fix it.

  • Michael Taylor 0

    While I do like getting a new VS version, for those who have to pay for it there really isn’t any killer features in VS 2022 that makes upgrading from VS 2019 worth it. The change to x64 is probably the biggest change but there is going to be extension issues for a while related to this as it is a big change. I expect lots of hotfixes to VS 2022 to resolve issues with both internal tooling and external extensions.

    The only thing that makes my team remotely consider upgrading to VS 2022 is .NET 6 support as it only works on VS 2022, a bad decision in my opinion. Since .NET 6 is a LTS (and .NET 5 wasn’t) then MS is pretty much forcing everyone to shell out money for VS 2022 with almost nothing to gain by it other than LTS support in .NET 6. I envy the C++ folks right now. They can just use the build tools to upgrade and continue using VS 2019. Not really a fan of the new MS approach to forcing software sales (or the purchase of Software Assurance).

    • Mark DownieMicrosoft employee 0

      Hi Michael,

      Hot reload and AI assisted whole line completions are just two of the features getting some really positive community feedback in Visual Studio 🙂

      We have been working really hard with our extension partners to ensure we have included many of the community favorites. Please don’t forget to share your feedback under Issues!

      With the GA release of Visual Studio 2022 we are recommending customers upgrade from earlier versions of Visual Studio, we also understand that is a process with multiple considerations for some teams. Note, Visual Studio 2022 uses the same licensing model as 2019. To use Visual Studio 2022 Professional or Enterprise editions a valid license will be needed.


      • Yoonjeong Jo 조윤정 0

        What do you mean by “Visual Studio 2022 uses the same licensing model as 2019” in your comments? Does this mean that visual studio 2019 and 2022 can use the same license key? (Delete 2019, then install 2022)

  • Michael Taylor 0

    I should also mention that, now that VS 2022 is x64, when it eats up available resources Windows goes down. Running VS 2022 over the weekend resulted in me having 98% of system resources used which brought down Windows. Whereas before if VS ran out of memory it just crashed, now it brings down Windows. Not sure this is a step up. Fortunately it only happened once, couldn’t do any reporting because Windows didn’t have any system resources available. This is with pure VS, no custom extensions so good luck debugging that. Even after killing VS in Process Explorer I was still at 75% resources used even though none of the other apps were using much. Rebooting was the only real option.

    • Anthony CangialosiMicrosoft employee 0

      I’m sorry you’ve seen VS and Windows crash. It’s still worth reporting these issues by submitting feedback from VS, even after the fact. VS will still collect logs that can the engineering team can use to investigate along slide Watson data, improving the chances and speed of resolving these issues.

      • WM Z 0

        You don’t need logs.
        Open a somewhat large solution, edit some documents then close them, and even the whole solution, you will notice the memory consumption increased.
        By using WinDbg, you can see that some WpfTextView instances were not released even if all code editor windows have been closed. It seems that the problem has something to do with the AutomationPeer in WPF. Details in my another reply around here.

    • WM Z 0

      Hi, while I was developing my VS extension Codist, I also noticed the memory leak. Firstly I thought it was a problem of my extension, and tracked it down with WinDbg. After fixing all possible memory leak points, I found that the leak persisted. Then I fresh-installed a VS 2022 and saw that memory increased as we open-edit-close documents.

      In the issue tracking of my extension, I wrote down something with WinDbg. It was not absolutely the problem of VS, maybe it was caused by the WPF framework and lasted for years! The bug was reported in August this year by another user and I had added my findings there too.

  • valleeefar 0


    looks great so far. Just a short question: will there be a perpetual standalone-license for the professional edition of VS 2022 ? The link on the pricing/product page still leads to the VS 2019 edition.


    • Anthony CangialosiMicrosoft employee 0

      Thanks @Valleeefar.
      Yes, a standalone version of VS 2022 Professional will be available in the coming weeks.

      • valleeefar 0

        Thanks for your quick answer, that’s good news. This is really important for small developers/companies that don’t want or need to go down the subscription route. Even for my private coding, I prefer the professional version to the community edition.

      • Peter Butzhammer 0

        That is great news. I understand that Microsoft wants to force us into subscriptions, but it would still be great if this were mentioned somewhere in the pricing information.

        It there any estimate when the coming weeks will come?

      • Germain Puccetti 0

        Not to burst your bubbles but I’ve been trying to reach their store all Tuesday and Wednesday and the few times I did not get the runaround, I’ve gotten all kind of answers: from standalone will be released April 2022 to not available anymore. I’ve tried the MS store by chat, email and phone. I’ve tried their subcriptions phone and email (Rance) just to be told I contacted the wrong department (Why again is the standalone purchase under their individual subscriptions? and yes it’s still 2019). On Monday, Microsoft still had a link under purchases which said ‘buy perpetual standalone license of VS 2022 Professional’ which lead to VS2019 Pro. After I brought it up with them, 2h later the link was changed from 2022 to 2019 and a few hours later removed.
        I’ve been programming in Visual Studio C++ since 1998, and microsoft’s service has become worse and worse. It was the same behavior of microsoft 2 yrs ago when releasing VS2019. The standalone pro version was released 2-3 weeks later because of programmer complaints. Now, they are pushing for higher sales in subscriptions to Azure even if we don’t want it. From a friend working at MS, as long as they don’t reach their Azure sales target, the standalone version will not be released. Sad but true.
        I expect MS behavior will become even more disrespectful at their next release of VS. There is good news though, Nvidia is releasing software platforms / IDEs for developers of deep learning / ML solutions in R and Python. No need for Visual Studio.

      • Vyacheslav Lanovets 0

        Hello. I wonder if more specific schedule can be provided? This information would really help with planning both budgeting and technical development.

  • Matt O 0

    Unable to find SSRS (SQL Reporting Services) and SSIS (SQL Server Integration Services) extensions for VS 2022.

    Nor can I find the feedback or backlog items for this functionality.

    What is the ETA on these as we can’t fully upgrade to VS 2022 without these two features.

  • Tim Belvin 0

    I am excited about a lot about VS 2022. But am also disappointed. With a clean install on Windows 10, using the Maui template fails to build regardless of the target. And help for the errors I was getting was not easy to find. I simply could not build the demo Maddy gave in her talk on the Maui features – it does not work out of the box.

    I realize Maui will not GA until sometime in 2022, but that template should have delivered a buildable project out of the box.

    I was able to build a couple of other projects to play with some of the new features – so still worthwhile

    • Maddy MontaquilaMicrosoft employee 0

      Hi Tim! This is weird, are you using VS 2022 Preview? Can you go to Help > Report a Problem and file this?? It did work out of the box for me when I just tried it so there might be something weird going on and I’d love for the engineering team to be able to take a closer look!!!

  • David Dos Santos 0


    A significant amount of the work we do it’s with SQL Server Data Tools (SSIS, SSRS, SSAS). After installing VS2022 Enterprise, we noticed there is compatibility with SSIS, SSRS, SSAS in VS2022.

    Would you please advise if VS2022 will allow development with SQL Server Data Tools?

    Thank you,
    — David

  • Yoonjeong Jo 조윤정 0

    I am using a Visual Studio Professional 2019 license key. Using the same license key, can I delete Visual Studio Professional 2019 and get Visual Studio Professional 2022?

    • Eli Black 0

      I don’t think so.

  • Kasinath Conjeevaram Ravi 0

    Can’t wait to try this out and the new .NET 6 eco-system!😊👌👍

  • cs 0

    Congrats to the DevDiv team, and thanks for all the hard work….exciting times again.

  • Cesar Maroun 0

    Why was the default theme changed to the less comprehensible and less productive dark mode?!

    It is a fact that dark mode makes you less productive for absolutely scientific reasons.
    Light when there is light, Dark when it’s dark. That’s what most systems have finally understood (Android, Mac OS, etc…)

    You just made every product less productive (No way of convincing the developers that it’s just a hype now).

    The selly “less eye sore” argument has nothing to do with being productive.

    • Gavin Williams 0

      I’ve never heard this argument before. Let me try to answer … because dark theme!

  • Eugene Kuchynski 0

    Was waiting for new VS and NET, but in fact got absolutely incredible behavior in the form of 100% usage of CPU and memory (i7 9750H – 16Gb) with pretty average Blazor server project, non-working hot reload and EditContext which tries to validate public fields (not properties) throwing ArgumentException (type does not contain a public property named …). Upon reaching any breakpoint, clicking Continue leads to never-ending “Checking code changes” message. This all turned my pretty powerful laptop into an old bucket not reacting to any clicks.
    As for me, after months of waiting for this release which includes so important and long-awaited improvements, it turned into complete fail 🙁

    • Krešimir Grozdek 0

      I have exactly the same experience, even with latest update :(((

  • JohnGough Gough 0

    I’m very impressed with how much smarter IntelliCode is. Very impressed. I’m sure it will get even better over time.

  • David Dos Santos 0

    So far, I’m not impressed because when I’m creating a new project it stands by for minutes.

    My VS2019 works like a champ with SSIS, SSAS, SSRS, anybody else having issues with VS2022 Enterprise?

  • Hristo Hristov 0

    Let’s hope that there are a real Visual Studio, Windows and dev tools for Windows on ARM in the works.

  • Łukasz 0

    I have VS 2019 Enterprise edition.
    Is that possible to refactore key from 2019 to 2022??
    Now i see that is now working and the trial is only available.

  • Robin Wilson 0

    I’m pleased this is out but it would appear that missing is compatible versions of Reporting Services, Analysis Services and SQL Integration Services and I don’t know why they still aren’t rolled into the main installer checkboxes rather than separate addons.
    It always confuses IT departments and usually wastes a day to get the extra bits installed where admin access is not granted.

    • Chuck Ryan 0

      I can understand that these services are out of sync with VS as, correct me if I am wrong, they are tied to the SQL Server release, not VS. But there is no reason VS cannot load the latest version at release, they are being shipped as an extension after all, they just choose not to.

  • Alfred J 0

    How do you upgrade VS 2019 community to VS 2022?
    VS2019 community doesn’t upgrade thru the VS programs auto or manual update and when i try to download the VS 2022 community from the link to reinstall, as it is 64bit, and it is the same download as the 2019 from October 2021.

  • Massimiliano Rossi 0

    be good at advertising such a product. and do well. however, can you explain to me how you can expect a developer to use VS without having a minimum of support for creating and managing RDLC reports? do you think we do applications without being able to print? and to think that you have taken this path for years now.

    but do me the favor … use other dear colleagues

  • Kelvin Mwenda 0

    With visual studio 2022 i cannot drag and drop client side libraries from solution explorer to _Layout file in core 6.0.My pointer is displaying the disabled icon.

  • Arvind Knudsen 0

    It seems like post-build event macros are no longer working?

    I’ve got this command:

    xcopy “$(TargetDir)*.dll” “$(SolutionDir)MyProject\$(OutDir)Modules\$(ProjectName)\” /D /Y /E /I

    And it’s not doing anything, nor is it resolving anything?

    Also – it was very helpful to see the available macros and what they resolved to in the previous versions of VS…

  • Robert Ayotte 0

    Just my 1.5cents. (inflation)
    was running vs2022 community (preview) and all was going well!
    vs2022 was released, uninstalled preview (best as ms will uninstall)
    installed vs2022 Pro.
    not (1) app works. all worked well being developed in (preview) now
    just creating a “blank” single page mobile (android/ios) and first build
    with only items ms uses to create app i always get (minimum) 30 errors.
    #1 error is ….C#7.3. it wants version 10???????????????????????????????

    finially giving up on this release, will have to format machine and go back to vs 2017
    were everything (including preview) worked!!!!!

    very disappointed in the vs team? total let down on a product that is error driven

    my 1.35 cents, inflation!!!!!

    • Midnight 0

      I guess the latest 2019 would be fine to cover any needs before .NET 6 become popular. Also C# is fully bacwards compartible. It means #7.3 must work fine in #10 build, anyway I didn’t notice any breaking changes regarding to this.

  • Midnight 0

    What is `Current` channel? When the Release version will be available? Is Current = Release? Why it was renamed? Why do you show in Installer `Visual Studio 2022 Current` instead of `Visual Studio 2022`? Is it a warning for me that i must pay attention to the delivery channel before use? I can’t catch the idea.

  • Chris Botha 0

    I want to buy a standalone license for Visual Studio 2022 Professional, not a monthly subscription. Where do I find that? Thanks.

  • Krešimir Grozdek 0

    Unfortunately, for me this is the worst version since VS2003. I have catastrophic debugging experience with constant freezing of VS2022 while trying to debug anything in Blazor server project. I’ve also noticed abnormal resources (RAM) consumption, and after few hours whole windows system slows down and crashes.
    Development experience is really frustrating. I spend 80% of time wrestling with VS.NET, and 20% doing actual coding.
    VS2022 is real disappointment.
    btw. I have 16 Gb od RAM, CPU AMD Ryzen 7 3700X, Windows 10 Pro 10.0.19042 Build 19042 and VS.NET 2022 Community – Version 17.0.1
    That should be enough resources, doesn’t it?

  • andrei-pancu 0

    Is Team Explorer being phased out? Essential functionality appears to be missing. For example, how do you initiate a pull request?

  • lei li 0

    Unfortunately, there is no corresponding WDK version support

  • McCollough, David M. 0

    So today, I went to Tools -> Android -> Android SDK Manager and nothing higher that 8.1 (oreo) shows up. How do I fix that?

  • Jamal Assaf 0

    Unfortunately, VS 2022 constantly freezes and CPU memory CPU spikes to 100%. I opened an issue, but the Feedback BOT closed it because it thinks it is a duplicate!
    Sometimes, merely clicking the mouse, VS just freezes and I have to the end the task in Task Manager!
    I even tried VS 2020 17.1 preview which immediately froze upon the first mouse click in the source of an aspx page!!

    Despite all the good features, VS 2022 has been so far frustrating and unusable. Going back to VS 2019 for now.

  • Daniel Fitzgerald 0

    Congratulations to everyone involved in this release of such an incredible product. 64 bit is huge and I am looking forward to seeing the performance benefits.

    I only downloaded and installed it yesterday, and recompiled several of our ASP.Net Web Apps, all without any issues – they all ran fine in IIS.

    Kudos all around 🙂 Great Christmas present!

  • mi ka 0

    Does vs2022 output console.write() to output window? (like 2017 does), thats my only reason to keep using 2017 still..

  • Jean Piloso 0

    Buenas Tardes, el reporte RDLC ya no se encuentra disponible que sucedió ya no va a salir?? o existe otro tipo de reporte que pueda utilizar ??

  • Valery Boronin 0

    Please, rebuild your WDK extension for 2022 and return WDK support as we can’t build driver projects in 2022, it prevents us from moving from 2019 for daily use.

  • Aleksandr Vaysberg 0

    What about Copy Website option? Can I copy a web site the same way as it used to be in VS 2017?

Feedback usabilla icon