Visual Studio 2022 Preview 1 now available!

Justin Johnson

We’re excited to announce that the first preview release of Visual Studio 2022 is ready to install! This is the first release of a 64-bit Visual Studio and we’d love for you to download it, try it out, and join us in shaping the next major release of Visual Studio with your feedback.

Our key goal with this preview is to test and tune the scalability of the new 64-bit platform! With the new 64-bit platform Visual Studio is now capable of scaling to make use of all the system resources you have to improve the reliability of Visual Studio especially when working with complex solutions or using Visual Studio over long periods of time. The 64-bit conversion effort affects every part of Visual Studio, so the scope is much bigger than our usual previews.

We know that you expect quality, stability, and scalability from Visual Studio. And to be totally transparent, the quickest way for us to get there is when real developers like you tell us where we can improve. We really do pay attention to every bug report, suggestion, and upvote! Which you can submit from inside Visual Studio via report a problem.

Report a problem with visual studio
Help us improve the quality and stability by reporting a problem within Visual Studio

The Visual Studio 2022 previews can be installed side-by-side with earlier versions of Visual Studio, are available in all three editions (Community, Pro, and Enterprise), and are free to use.

We need your feedback

We encourage you to try out the preview and use it just like Visual Studio 2019. We appreciate your time in providing feedback and completing in-product surveys, which are invaluable in making Visual Studio 2022 the best developer environment for you.

We would particularly love to hear about your experiences working with very large and complex solutions in Visual Studio 2022. Before the 64-bit upgrade, customers with this kind of solution would sometimes experience issues with Visual Studio as it ran out of memory to use in the main 32-bit process. During early testing of Visual Studio 2022, the same customers were able to run the IDE for days, even with solutions containing 700 (or more!) projects.

What’s coming

Because most of the Preview 1 upgrades have to do with 64-bit support, we’ll be releasing an exciting slate of new features and performance improvements starting in Preview 2. You can read all about those upcoming features on the Visual Studio roadmap. One new feature you can try right away is the update to IntelliCode – you can automatically complete code, up to a whole line at a time.

There’s still some work left in moving Visual Studio to 64-bit, and a small number of the features in Visual Studio 2019 are not included in Visual Studio 2022 Preview 1. You can find a list of those upcoming features in the release notes.

During the Visual Studio 2022 preview, our partners who build the extensions that you use and love will be working to update their extensions. While they do that, their extensions won’t be available in Visual Studio 2022 right away.

The first preview of Visual Studio 2022 for Mac will be coming soon, giving you a first look at the new modern macOS UI for Visual Studio. We still have some work to do before we feel it’s ready for developer feedback and we’ll keep you updated on its progress here on the Visual Studio blog.

Calling all extension authors

If you make extensions, we want to help you get your extensions into Visual Studio 2022. To get you started, check out our guide to migrating your extensions to Preview 1.

Also! This Friday, June 18, you can watch Mads Kristensen, a senior PM on the Visual Studio team, demonstrate how to update extensions for Visual Studio 2022. The livestream starts here at 3 p.m. Pacific time: https://youtu.be/-PKIPTW6km0

We’ll continue to share details with our extension authors and maintainers as we get closer to the official product release for Visual Studio 2022. If you have any thoughts about how we can make this process better, you can share your thoughts on this short survey.

Help shape Visual Studio 2022

Take part in shaping Visual Studio 2022 by installing it, using it, taking part in surveys, and sharing your thoughts on Developer Community.

70 comments

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

  • Erik Ejlskov Jensen 0

    Link to extension migration guide is broken

      • Erik Ejlskov Jensen 0

        Missed bottom link

    • anonymous 0

      this comment has been deleted.

  • Piotr Karczmarz 0

    This was quick! The first announcement about public VS 2022 Preview mentioned the summer but I wasn’t expecting anything earlier than July/August. Impressive! Downloading starts now … !


    Piotr Karczmarz, CTO at ContextKeeper.io, building VS plugin allowing to instant jump to deep work via “mental snapshots”.

    • Justin JohnsonMicrosoft employee 0

      The team has been working hard on the conversion process! Thanks for your comment and I hope you enjoy the first preview of VS 2022.

      • Piotr Karczmarz 0

        I must say I’m really impressed by the quality of the VS 2022 Preview build and how smooth VSIX porting experience was. It simply worked out of the box despite the fact that ContextKeeper uses a lot of internal VS APIs to do its magic and I was prepared for long days and hours to port it to VS 2022. Wow!


        Piotr Karczmarz, CTO at ContextKeeper.io, building VS plugin allowing to instant jump to deep work via “mental snapshots”.

      • Adam Lunga 0

        Hi

        Just wanna find out if SSIS is integrated with this preview

  • Luiz Fernando 0

    Nice! 🙂

  • Praveen Potturu 0

    Nice to see this ready to try but bad that I don’t have hard drive space to install it.

  • Federico Berasategui 0

    Please Microsoft, Please, get rid of the horrendous XML abomination required to define new buttons/commands in Visual Studio’s Menu. Or keep it abstracted underneath if really needed, but please don’t shove it down our (extension authors’) throats. Give us a sane, easy to use, understandable, discoverable, statically typed, intellisense-enabled C# API instead.

    Also: Why am I still paying for MyGet? might seem like no big deal from your perspective, but for small software companies in third world countries, it’s an additional burdensome cost. Please allow me to host my own private VSIX feed on Azure Devops Artifacts, just like I’m using it for Nuget packages.

    • Piotr Karczmarz 0

      100% I share similar feelings. Adding a context menu or something as simple as command button to a tool windows is such a pain. Thousands of groups, parents, guids, symbols etc. to make simple button or command entry. And there is no way to debug it, you could only run it and pray that will work. Definilty huge pain point for VSIX developers.


      Piotr Karczmarz, CTO at ContextKeeper.io, building VS plugin allowing to instant jump to deep work via “mental snapshots”.

      • Leslie RichardsonMicrosoft employee 0

        Thanks for your feedback! We are currently working on improving the command definition experience via our new, upcoming extensibility model and Mads Kristensen’s upcoming VS SDK Community Toolkit. We will share additional info about both projects in the near future.

  • 国强 冯 0

    Sorry ,Resharper is better than VS!

    • PandaSharp 0

      You cannot use Resharper without VS

      • Jan Děták 0

        He certainly meant Rider.

  • Daniel Smith 0

    Wow, I’m really impressed! I’ve been testing various project types, and loading all my existing solutions, and everything just works.

    Honestly, I was expecting some older project types to be missing, legacy designers to be broken etc. but I’ve not hit a single issue so far.

    Congrats to the team for all the hard work porting to 64-bit, and delivering a super high quality 1st preview release. It looks like you’ve got a really solid foundation, and I’m looking forward to see how things progress before RTM.

    • Ahmed Hemdan 0

      I did the same and it was impressive. Have you tried creating a new project using VS 2022, it wasn’t able to do that also it broke all other VS 2019 versions I have.

      • Daniel Smith 0

        I’ve created numerous new projects in VS2022 and they’ve all worked perfectly so far e.g. WinForms (both Framework 4.8 and .NET 6), console apps, ASP.NET Core Web apps, Blazor Server, etc. What type of project were you having trouble with?

        My VS2019 instance wasn’t affected at all by the VS2022 installation. Sounds like you’ve maybe got a corrupt installation. Maybe worth uninstalling both products, and then try a fresh install?

  • Jeremy Morton 0

    As a former Builder in DevDiv, I didn’t know if I would ever see the day where a 64-bit devenv.exe would be released; the amount of work, both on the product itself, and then getting the ecosystem to support it, was always daunting.

    I like to think that, somewhere, Dave Cutler is smiling.

  • Huo Yaoyuan 0

    Please, don’t always change the icon at major version. Only change it when the design is updated.
    The minor change that make it distinguishable with previous version often make the good design worse. Distinguishing versions by icon shouldn’t be a good request, as different SKUs of the same version can already be installed side by side.

  • Mohsen Afshin 0

    New era of compilation started, Thanks Microsoft!

    • Théophile KAPAPA 0

      nice.

  • Paulo Pinto 0

    > One new feature you can try right away is the update to IntelliCode – you can automatically complete code, up to a whole line at a time.

    As if, IDL keeps being ignored, despite WinDev forcing us to deal with to for the past 25 years.

    This situation got even worse after you decided to replace C++/CX with C++/WinRT without giving us comparable tooling.

    Looking forward to Visual Studio 2022 finally offering a development experience that can match what C++ Builder has been offering to C++ developers on Windows since 1997.

  • PandaSharp 0

    Maybe it’s only me, but there is one small thing that annoys me: why do we have still “SQL Server Express 2016 LocalDB”? Can we have a 2022 version or get rid of the “2016”? Thanks! 😀

    • Daniel Smith 0

      I noticed this during setup too. 2019 Express Local DB is the latest available and it’s highly backwards compatible so can’t see why they’d still be bundling 2016.

      • Michael Taylor 0

        My understanding is that the first preview is literally just getting VS 2019 compiled as 64-bit with whatever changes were needed to get the core tools up and running reliably. Beyond .NET 6 being enabled but not .NET 5 I don’t see any major differences between this preview and the VS 2019 final preview version. I would expect the dependencies to be updated in later sprints.

        • PandaSharp 0

          I hope so, I pointed it out because this was already bothering me in VS 2019 XD

  • ODOM IFEANYI 0

    This is super amazing. Microsoft always on point

  • Zehev Spitz 0

    Are there changes/updates planned for the Debugging Visualizer API?

    • Andy SterlandMicrosoft employee 0

      No plans to announce yet. If you have any suggestions for improvements, please open a suggestion ticket on developer community.

  • Sod anakin 0

    Would love to use it but….

    It doesn’t work. I opened a Net 5 project and it keeps complaining about

    The runtime pack for Microsoft.NETCore.App.Runtime.win-x64 was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'win-x64'.

    Nuget restore does nothing.

  • Prayaas Aggarwal 0

    Shouldn’t the article say the first x64 or AMD64 version of Visual Studio? 😊 While it is the first 64-bit version, it doesn’t run natively on all native 64-bit platforms that Windows supports, namely ARM64. Great job with this release. I’m excited for VS.

  • Ramtin Jokar 0

    Installed it just now.

    I hoped that you changed the new project Template to something new or something like VS17 or older versions, because in VS 19 was very messy and in VS22 still is!

    Change this template please.

  • Jacques Erdey 0

    Thanks Justin. A blog post about the tech stack used to develop VS 22 would be interesting as well.

    • Justin JohnsonMicrosoft employee 0

      Thanks for the idea, I will bring this up to the team!

  • Michael Bond 0

    First impressions are good. I fired up our product and it seems to load much faster. I’ll give it a solid workout later. One personally major regression though is the mandatory presence of the new GIT interface with no apparent way to revert it to the older Team Explorer interface. Having the “Team Explorer” tab but with links to the poorer GIT Changes interface is not a good look in my opinion. By all means make it a default so those who are unaware can suffer the new interface but let me revert it back when I want to.

  • Andrew Truckle 0

    Can I install VS 2022 Preview and continue to use VS 2019 on the same PC?

    • Andrew Truckle 0

      Yes!

      “You can install and use Visual Studio 2022 alongside previous versions of Visual Studio, including Visual Studio 2019, Visual Studio 2017, Visual Studio 2015, Visual Studio 2013, and Visual Studio 2012.”

      • Michael Bond 0

        I’ve been running it now for a few hours and there are so far no apparent issues running it side by side. I’ve had an existing solution open in 2019 and 2022 at the same time without a hiccup.

      • Pieter Siegers 0

        Is that your answer or Microsoft’s claim?
        What about all the other software we have installed to do our daily dev work?
        Have all possible combinations been tested?

  • Ioannis Alexopoulos 0

    Great stuff, it looks sharp and responsive, but the new Dark Theme and Icons looks horrendous compared to existing one. Also, the Git Experience is confusing. Amending a Commit is very unfriendly. Please do not abandon the Azure Dev Ops for GitHub. GitHub luck tons of functionality like Testing etc…

    • Pratik NadagoudaMicrosoft employee 0

      Hi, can you explain what is unfriendly about Amending, perhaps through a feature suggestion, so that we can diagnose and have a targeted conversation there. Also, we’re not abandoning Azure DevOps. We did prioritize building new GitHub features first in the early iterations while testing this new experience. But we hear the feedback loud and clear from Azure DevOps customers. So we’re planning to keep the existing and past Azure DevOps functionality in VS 2022.

  • Alejandro Escudero 0

    Nice. The first thing it did was to messed up my Unity installation. Awesome

  • Koby Kahane 0

    When is a release of the Windows Driver Kit that’s compatible with Visual Studio 2022 expected? In particular, the current WDK VSIX is incompatible.
    Perhaps more generally, why is the WDK still a completely separate download and not an individual component installable via the VS Installer like the Windows SDK is?

  • Andrew Truckle 0

    My MFC project built fine but the C# projects complained about Newson JSON conflicts between 4.0 and 4.2 and it refused to accept the signed PFX file.

  • lank b 0

    I just want to know when I can add a Chinese language pack, I think those Chinese people who are not familiar with English, will feel sad. You know what I’m talking about, don’t you, bro

  • Super Coco 0

    Really not fixed the unuseable New Project Dialog chaos mess replacing by the old tree based “New Project Dialog”?
    Really not fixed the unuseable modal Start Screen replacing by the old good Start Page?
    Really continue setting ON by default the “Compact Title Bar”?

    No one likes or demanded this New Project dialog or this new Start Screen:

    https://developercommunity.visualstudio.com/t/vs-2019-preview-new-project-dialog-is-unstructured-1/401508
    https://devblogs.microsoft.com/visualstudio/redesigning-the-new-project-dialog/#comments (Read the comments)

  • Eugene Ivanoff 0

    Still same bugs… Quick pressing Ctr+X makes VS hang. Almost always the VS icon in Task Bar disappears upon first project load. Closing and opening project makes icon appear. Awful coloring of Razor keywords in Razor cshtml files in new dark theme.

  • Cesar Armando Fong Espinola 0

    When i download the visual studio installer only shows me visual studio 2019 preview . i am running amd64 any help on this?

  • John Moreno 0

    Report projects don’t seem to work…

  • Jaroslav Smid 0

    Purchase model will remain same as VS 2019? Particulary, will perpetual license still be available? I would really hate being forced to any kind of subscription.

  • Daniel Hughes 0

    What is the progress on Visual Studio for Linux. It has 998 upvotes in the Developer Community, making it Visual Studio’s second most requested feature.

  • Shah Tirth 0

    In visual studio 2022 .aspx has no auto intelligent for Cascading Style Sheets in not working properly…Please Check it.
    In big fan of latest visual studio & visual studio code

  • Mike Diack 0

    Suggestion/Feedback (will raise as a bug separately):

    VS 2022 Preview 1’s IDE will only run on 64 bit development systems, but by default the compiler run (cl.exe) when compiling C++ code using VS 2022 Preview 1 is the 32 bit compiler toolchain, targetting either 32 or 64 bit systems.
    Given that MS have long had a 64 bit hosted compiler toolchain, and that already you are expecting the system running the IDE to only be 64 bit, would it not make more sense to use the 64 bit compiler to generate 32 or 64 bit target code (to get more performance and take advantage of more memory during compilation and linking?).

    (I know you can force use of the 64 bit toolchains via environment variables, in older versions of VS, namely the following 2 environment variables:
    PreferredToolArchitecture
    and
    _IsNativeEnvironment
    )

    Cheers, Mike

  • KillerBoy KillerBoy 0

    just not quickly
    same machine, same situation
    community edition (2019 with extension: codemaid, anksvn, indent guides; 2022 no extension added)

    only for project list vs2019 7.31″ vs2022 13.66″
    reading a solution (4 projects, 4 files opened, ~150000 files in total) vs2019 21.03″ vs2022 51.59″
    closing the solution without (no modification, no questions) vs2019 5.85″ vs2022 10.65″

    test2
    launch and open one solution (11 projects, 11 files opened, ~3700 files in total) operative in vs2019 33.04″ vs2022 40.11″

  • The Sharp Ninja 0

    Are there official logos or other art assets that blog authors can reuse?

  • Álvaro Aguilar Romero 0

    Lo instalé para verificar la existencia de los componentes de Data Tools…
    Aún no existen las extensiones para SSIS, SSAS ni SSRS, por lo que en este momento, no es de interés para mí.
    Probaré nuevamente en el futuro próximo,

    Saludos.

  • John King 0

    Make VS run under .net 6 please !
    Why the .Net[Core] born many years, and even Microsoft is not using it ?

  • Robert Gale 0

    You write, above that [users of VS expect] “stability, scalability and quality”. This is a strange misapprehension on the part of the author as VS has become, over the past decade, notoriously and increasingly UNstable, UNscalable and shabby. The great hope is that the frustration of endless hangs, crashes and spurious, sometimes bizarre, but always unhelpful error messages will be reduced in 2022. Too much time in VS is spent waiting for the tool to come back to life, and too little engaged in the joy of coding; the reinstatement of the latter being one of the primary goals of the plethora of competitor, lighter-weight tools gaining ground (many of which are also free).

  • Achmad Sudibyo 0

    Hi, what about unreal engine developer with the improvement of c++ can it on par with jetbrain rider for unreal engine or vs with paid addon such as resharper or visual assist?

  • Bob Elward 0

    Glad to see Visual Studio move to 64-bit, thanks to all that worked on it!

    Now that VS is 64-bit will we see the maximum size of C# array increase beyond 2 billion?

  • Игорь Баклыков 0

    You know what? CMake from VS 2022 can’t create generator “Visual Studio 17 2022”. But I can’t force VS to use custom installed CMake 3.20.0 which can do that!

  • Felipe Villela 0

    I teach classes with Visual Studio and it’s embarrassing how often screens hang, things stop working and I have to restart VS, delete .VS folder, delete bin/obj. It makes me sad =/
    I used to joke that was a problem only with java, so it’s a hard pill to swallow, even more because I love dotnet. It’s a really bad impression for all new students.

  • lin Json 0

    When will the Chinese language pack be released?

  • Pieter Siegers 0

    Just a simple Q upfront, can I install and not disturb other VS installations like VS2019??

  • Jorin Gedamke 0

    What I would like is an app that doesn’t need to use all the system resources, i.e. one patterned on Linux software. There the idea is to “do one thing well”; here’s it’s “do everything well”, and it shows.

Feedback usabilla icon