Microsoft to Launch Visual Studio 2022 on November 8

Posted on October 12, 2021 by Paul Thurrott in Dev with 16 Comments

Microsoft will launch Visual Studio 2022 on November 8. And it has released near-final versions of the product and some .NET 6 solutions.

“I’m excited to announce the upcoming release of Visual Studio 2022 on November 8, and the immediate availability of the Visual Studio 2022 Release Candidate (RC),” Microsoft corporate vice president Amanda Silver writes in the announcement post. “We invite you to explore the latest capabilities of Visual Studio 2022 at our virtual launch event on November 8. Throughout the day, you can learn from some special guest speakers, talk back to the Visual Studio team, and even download exclusive digital swag.”

The virtual launch of Visual Studio 2022 kicks off at 8:30 am PT/11:30 am ET on November 8 and will feature a keynote address featuring Scott Hanselman, the Visual Studio product team, and Ms. Silver. There will be various technology-based breakout sessions, tips and tricks talks, and live Q & A’s throughout the day.

Developers who are interested in Visual Studio 2022 can download the Release Candidate (RC) version today. It’s fully supported by Microsoft with a go-live license for production use ahead of general availability (GA) next month. (And you gotta love that at least one part of Microsoft uses the appropriate terminology for release milestones.)

There are also a lot of .NET 6-related milestone releases to test today, including .NET 6 Release Candidate 2 (including some ASP.NET Core updates) and .NET MAUI Preview 9. As you may know, Microsoft will deliver .NET 6 in November too, but .NET MAUI won’t ship until mid-2022.

Tagged with , ,

Join the discussion!


Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Comments (16)

16 responses to “Microsoft to Launch Visual Studio 2022 on November 8”

  1. joeawilliams

    Is this the version that is going to be a 64bit application? Not that I care but just wondering and how that affects VS plug-ins. I guess I can download it and figure that out.

    • scottkuhl

      The old extensions will not work. Developers need to at a minimum recompile them and some need significant updates. It’s definitely a thing to be aware of. Not all extensions will be there.

  2. blue77star

    They are already on .NET 6 version. Former .NET Core and now .NET 5/6 did not really take off in the industry. Those .NET 4.8 Framework Web Forms seem to have much longer life than anticipated.

    • shameer_mulji

      I'm much more intrigued to see how well .NET MAUI will work when officially released.

      • saint4eva

        I think it will work very well, considering that they switched to handlers from renderers. This allows them to make a lot of performance changes and innovate. And, it has made it easier for more app model to be built on top of .NET Maui e.g. Fabulous, Control, Comet, Blazor, Tizen etc.

    • saint4eva

      I believe you are wrong on that. A lot of people are moving to .NET Core/ .NET 5, notwithstanding some solutions are still on .NET Framework. And some apps would forever remain on .NET Framework.

  3. rmac

    I'm sure VS 22 and .NET 6 are full of awesome goodness but I just wish MS would focus on a common control stack - one UI - that would run on Windows and web to compete with Flutter. For me, without that it's looking like Core web services on the back end + Flutter.

    • rm

      You mean .NET MAUI.

      • rmac

        No I don't mean MAUI, because the web stack (aka Blazor) doesn't use WinUI but rather HTML and CSS. To further compound, the MAUI controls will be styled upon Fluent UI, and the Fluent UI counterpart for web controls is based upon React.

        • saint4eva

          Please ensure you know what you are saying before you do. WinUI is an UI stack for developing apps for Windows. However, cross platform solutions such as flutter, Maui or React Native targets Windows using WinUI. .NET Maui targets other platforms using their native stack e.g. MacOS using catalyst, Windows using WinUI. And there is a community effort going on for Linux using GTK. Also, Maui can do both native rendering and drawn UI.

    • saint4eva

      flutter runs on Windows using win32/ UWP. But flutter is moving towards using WinUI. Going forward, Windows UI (WinUI) would be the preferred stack for developing modern apps on/ for Windows. However, there are other efforts to provide cross platform solutions using WinUI e.g. Uno Platform. Also, .NET Maui is working towards providing a complete solution.

      • rmac

        Of course WinUI is a stack for Windows. FluentUI is a collection of UI stacks, one of which is WinUI for Windows. The irony is that Blazor desktop which will run atop MAUI will rely on the community, not MS, to provide a FluentUI for Blazor (and contrast that with the current stack for web which is FluentUI React). Similarly Uno was not written by MS.

        So I'm glad you finally 'got it' in when you took the time to respond to my first comment in the thread but ended up in a bit of a ravel. As I plainly said, I just wish MS would focus on a common control stack - one UI - that would run on Windows and web to compete with Flutter.

        • saint4eva

          This is open-source era. And it would not be too good for .NET is the community is not involved and participate and contributing to the growth of .NET. A solid company is developing UNO, and there are many other big customers behind Uno. WinUI team is going to solely focus on Windows as a platform, and the community can build on that to enlarge the Windows ecosystem. .NET Maui, Uno, Blazor, Flutter, ReactNative are some of the community efforts/ partners' effort. By the way, flutter is mostly good for Android and iOS. It is still working towards making their desktop and web stories an excellent one.

  4. robinwilson16

    Does anyone know if the reporting services addin will install into this version?

    I tried with the beta and it failed. Perhaps we need to wait for a new one of those too?

  5. blue77star

    The problem with .NET 5.0 and .NET 6.0 is terrible lack of libraries. I use ImageProcessor for .NET Framework. There is no remotely that powerful image processing API for .NET Core. It seems to me that people just don't invest into.