Visual Studio 2022 Preview 3 now available!

Mads

We are excited to announce the third preview release of Visual Studio 2022! With Preview 3 there are more new capabilities on the themes of personal and team productivity, modern development, and constant innovation. In this blog we’re going to highlight a few of the new capabilities of Visual Studio 2022 Preview 3. 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.

Personal & team productivity

In the Visual Studio 2022 vision blog we talked about delivering innovative features that revolutionize development is an important area for us to empower you to live your best developer life. In preview 3 we are adding new capabilities to some of the less used, but useful, features such as attach to process.

Attach to process improvements

One example is the improvements in the attach to process dialog. The dialog is now async, shows the command line arguments for processes, IIS information for w3wp.exe processes, and lasty the dialog has an optional tree view mode for showing parent-child process relationships. These capabilities reduce a lot of the friction in deciding which process to debug in advanced scenarios.

New project designer

With Preview 3 there’s a brand-new project properties designer for .NET SDK projects. The new designer is easier to use and browse with a single column of options with clear descriptions. Best of all the new designer has built in search so it’s now easy to find the property you need.

Text Description automatically generated

Dark theme improvements

In preview 3 you’ll see big changes to the dark theme to improve the usability of Visual Studio. The new dark theme has a new accent color, which is less intense, and used more sparingly to reduce distraction and eyestrain. The new accent color now matches the latest product visual identity, which helps you quickly find the right window when they are navigating among multiple tools.

A computer screen capture Description automatically generated with low confidence

Developing modern apps

With Visual Studio 2022, we are building tools to both support your existing applications and tools for building the latest types of applications. For example, in preview 3 we’re adding new capabilities to run tests in Linux environments and a new project types for frontend development with React and Vue.js applications using either TypeScript or JavaScript.

Remote testing

With remote testing you can now get feedback from your cross-platform tests, and even debug them from the comfort of Visual Studio! The feature works with a range of remote environments such as Linux containers, WSL, and over SSH connections – empowering you to test modern cross platform .NET applications.

A screenshot of a computer Description automatically generated

New JavaScript and TypeScript project types

The new JavaScript and TypeScript project types for Angular, Vue, and React make it easy to incorporate front end applications within your Visual Studio solution – empowering you to launch and debug your entire app from Visual Studio.

A screenshot of a computer Description automatically generated with medium confidence

Innovation at your fingertips

Another crucial part of our vision for Visual Studio 2022 is innovative capabilities that unlock your potential as a developer. As a developer some of the hardest issues to resolve are issues that only happen when your application is running live. To diagnose those issues sometimes all you have is a customer report that you can’t reproduce. If you can collect a memory dump of the issue, you can use Visual Studio to debug the memory dump, but that’s no easy task.

Diagnostic analyzer

Memory dumps are complex and finding the root cause of an issue is like looking for a needle in a haystack. With Visual Studio 2022 Preview 3 we’ve made that process a breeze – with the diagnostic analyzer. The diagnostic analyzer can be used on memory dumps to identify common problems seen in .NET applications. Empowering you to root cause complex issues in no time.

A screenshot of a computer Description automatically generated with medium confidence

Working with multiple Git repositories at once

Preview 3 is also getting new preview features such as multiple Git repository which enables you to work with a single solution that has projects in multiple repositories and contribute to them from a single instance of Visual Studio. This feature can be enabled from the `Preview` tab of Tools -> Options menu, just search for “preview” in the search bar (Ctrl+Q) and look for “Enable multi-repo support”.

One click publishing to Azure DevOps

In Preview 3 makes it easier to publish your code to Azure DevOps with the updated create Git repository experience. With a single click Visual Studio initializes a new Git repository and pushes it to Azure DevOps.

Image OneClickPublish

Summary

The features above are just a few examples of the direction we’re going with Visual Studio 2022. There are a lot more features to be explored in Preview 3. Over the next few weeks, you’ll see more blog posts coming for many of the new capabilities of Visual Studio 2022. If you can’t wait, head on over to the release notes to learn more about what’s new in preview 3.

Take part!

Visual Studio 2022 Preview 3 can be installed side-by-side with Visual Studio 2019 and it’s free for anyone to use while in preview. We want your help making Visual Studio 2022 the best developer experience for you, and we are excited for you to try out all the new productivity enhancements. We encourage you to download and use the preview just like you would use Visual Studio 2019 preview. We appreciate your time in providing feedback via Developer Community, reporting a problem, and taking part in surveys.

70 comments

Leave a comment

  • Joe Chang

    it doesn’t hurt to periodically strip a system down to minimum and reinstall everything, I would do a complete OS reinstall, but I lost my MS Office keys. Ok, on following the Prev 3 links to install, it says 2.1 , same as before install?

  • Mike-E

    Any word on plans to push extensions for 2022? I recall for 2019 there was a push to get extensions moved over from 2017 with developers. I am glad to see Mads move all of his already but his only account for 2 of mine, including the nifty Extension Manager, which I wish auto-converted extensions from 2019->2022. 🙂

    What about PowerCommands? They haven’t touched their code since 2018. :/

    https://github.com/microsoft/VS-PPT

    • Leslie RichardsonMicrosoft employee

      Thanks for the feedback. We have notified most extension authors with guidance and support on how to migrate their extensions to VS 2022, so it’s really down to each author’s individual timeline and resources as to when specific extensions will be published. PPT’s migration is currently in progress so you should see that suite of tools available soon!

      • Mike-E

        Thank you for letting me know, Leslie! It is very much appreciated.

        After some further investigation, VS-PPT is even worse than I thought. Power Commands is actually no longer a part of it and there doesn’t appear to be a GitHub for it? I hope that is being upgraded for the ride, too.

        In any case, I have made a vote here for others to upvote just in case. 😉
        https://developercommunity.visualstudio.com/t/Upgrade-Popular-MSFT-Extensions-to-VS202/1500844

      • Matthew Goffard

        It would be nice to get the Microsoft extensions updated as well, I use the installer projects extension quite a bit and between that and resharper (but that’s on jetbeans) being the 2 bigger hold ups on transition more fully, while mostly been using 22 for Maui experimentation

    • Joris Kommeren

      Looks like it got pulled, but the link in the header unfortunately seems to point to a ticket that was closed with a fix being a different version (16.11) instead of 2022 preview 3.

      Heck I wouldn’t mind if Preview 3 was republished in its broken state as apparently a modify in the installer would have fixed it

      • Nigel Booth

        I updated to preview 3 earlier and then had problems with VS2019 too. I was using a Windows 11 insider preview and thought maybe it was due to this so I have today gone back to windows 10 and then downloaded the VS2019 installer (16.11) which has failed and the VS2022 preview 3 installer which fails on VC_runtimeMinimum_x86.msi – this is a cached file that is inaccessible. Luckily I have both versions on another laptop and that is still working ok. I shall avoid any updates for now on there.

  • Gabe Wells

    I have updated to Preview 3 but when I open VS it hangs in a ‘Not Responding’ state.
    Will try to submit feedback via the Visual Studio Installer tool.

  • Luis Linares

    Hello! i have installed the new release and everything looks good! The installation was successfull!

    Now, I’m trying to install MAUI with this new version but i got an error 🙁

    I Ran maui-check and i got everything OK, but when i try to install maui, i recieve the message:


    Installing pack Microsoft.Maui.Controls.Runtime.win version 6.0.100-preview.7.1345…
    Writing workload pack installation record for Microsoft.Maui.Controls.Runtime.win version 6.0.100-preview.7.1345…
    Installing pack Microsoft.Maui.Essentials.Ref.win version 6.0.100-preview.7.1345…
    Writing workload pack installation record for Microsoft.Maui.Essentials.Ref.win version 6.0.100-preview.7.1345…
    Installing pack Microsoft.Maui.Essentials.Runtime.win version 6.0.100-preview.7.1345…
    Writing workload pack installation record for Microsoft.Maui.Essentials.Runtime.win version 6.0.100-preview.7.1345…
    Garbage collecting for SDK feature bands 6.0.100…
    Workload installation failed: The JSON value could not be converted to Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadPackId. Path: $.Id | LineNumber: 0 | BytePositionInLine: 40.

    • Damian Wyka

      Same here. First i had issue with single project extension for over 2 weeks on preview 6 preview (500 error) had to wait for whole next preview now maui workload installer is broken and still cant test maui ;/

      • MarcMicrosoft employee

        Can you both try renaming (or delete) your dotnet\metadata folder and trying the install again? We think there is an incompatibility with an older workload that was installed from a prior version of maui check that we’re not handling correctly. Note that any errors after the “Garbage collecting” message are likely not errors in the install of the workload but rather are errors in cleaning up prior workloads that were installed.

        I’ll try to get our release notes updated for this if you can confirm that solution works for you.

        • Aaron High

          That solution worked for me. I also needed to update maui-check. For reference, I deleted my metadata folder at ../Program Files/dotnet/metadata (since there are a few dotnet folders).

  • Michael M.

    PLEASE for the love of god. Make it possible to go to the old black theme. I pretty much hate the new one. It looks awful imo. 🙁
    I get change is good but seriously? changing a theme and then not saving the old one as a profile so people can use it if they dislike it?

        • Ray

          Don’t worry, you’re not alone. The stinky contrasts between background colors and (useless) outlines are just eye blinding. The colors are randomly smeared here and there. I would accept this as a good High Contrast theme, if at all. The new theme is dark in the sense of it being horrible.

          • Michael M.

            For me the icons on the right side
            Image
            were completely black until I hovered on them (I’m not using the “new” icons because they are not my cup of tea either)
            So maybe this was also overlooked? or just a me problem.

            //edit
            just remembered this now after using the old theme again.

  • 王宏亮

    When using vs2022 preview 3 with .net 6 preview 7, vs stuck everywhere.

    (devenv.exe, PID 1544, Thread 1) UIContextHelper.SetUIContext: The call to IVsAggregatableProject.GetCmdUIContextCookie failed. Error code: 1