Visual Studio 2022 and .NET 6 Support

News
14 October 2021

We have noticed a slight uptick in Microsoft Visual Studio 2022 and .NET 6-related support traffic. In this post, we'll take a closer look at what you can expect from DevExpress in our upcoming release (v21.2).

Visual Studio 2022 Support

First and foremost — yes, v21.2.3 will support the most recent Release Candidate build of Visual Studio 2022. Once Microsoft releases a final build, we'll update our release plans and make an official announcement on our website (we expect to offer official Visual Studio 2022 support in v21.2.4).

Like you, we have been testing our products against preview builds and we don’t expect to encounter any showstoppers (be they runtime or design time) prior to Microsoft’s official release.

DevExpress installers will ship separate VSIX extensions for Visual 2022 (alongside older versions of Visual Studio) to ensure that all major design-time tools (like the "DevExpress" menu, DevExpress Template Gallery, Project Updater, Toolbox, etc.) are fully functional.

CodeRush

CodeRush v21.1.6+ includes a new extension with Visual Studio 2022 RC support. You can download this extension from the Visual Studio Marketplace (the existing CodeRush extension supports Visual Studio 2015, 2017, and 2019).

Xamarin & .NET MAUI

Our free .NET MAUI or Xamarin.Forms UI controls will include a new Template Gallery (v21.2.3). Like other DevExpress application template wizards, our .NET MAUI/Xamarin.Forms Template Gallery was designed to simplify initial app setup.

Known Visual Studio RC 2022-related Issues (EAP and Beta 1 builds)

  • WinForms .NET: You cannot design .NET Core applications in Visual Studio 2022 RC/Preview. To use the design time in a .NET Core 3.1, .NET 5 or .NET 6 project, use Visual Studio 2019. This limitation applies to .NET 5 and .NET 6 projects only, .NET Framework is fully supported.

    11/10/2021: v21.2.3 (the Release build) fully supports Visual Studio 2022 Preview5/6. You can use the DevExpress.Win.Design package in both Visual Studios (2019 and 2022) to develop .NET 5 and .NET 6 projects.
    11/24/2021: Pressing the "Delete" key to remove a control at design time leads to an error. This issue is fixed in the v21.2.4 build.
  • Reports: At present time, our Report Designer is not available within Visual Studio 2022. We expect to offer complete Visual Studio 2022 support for both .NET Framework and .NET projects in v21.2.4.

    11/10/2021: v21.2.3 (the Release build) fully supports Visual Studio 2022 (RC3 Preview 7/RTM and newer builds). See the following help topic for additional information: Report Designer in .NET 5/.NET 6 apps.
  • XAF/XPO: We will support XPO's ORM Data Model Designer, XAF's Model Editor and Solution Wizard in v21.2.4 (we are awaiting stable versions of the Modeling SDK and other tooling. The good news is that some XAF/XPO users are successfully running their projects under .NET 6 previews today (learn more).
  • Documentation: The F1 shortcut does not open an online documentation page describing the focused control or API.

    11/23/2021: The F1 shortcut is functional in v21.2.4 or newer.

According to Microsoft, Preview builds of Visual Studio should not be used for production code. To better address your business needs, we’d love to learn more about your Visual Studio migration strategy. Are you using Visual Studio 2022 Preview/RC for production code today? Please comment below or post a ticket on the DevExpress Support Center. Your feedback will help us refine delivery schedules/announcements for future versions of Visual Studio.

.NET 6 Support

Our desktop controls/components (WinForms and WPF) support the latest Preview build of .NET 6. In addition, the DevExpress Template Gallery includes WinForms and WPF templates for .NET 5 and .NET 6.

XAF, XPO, Reports, DevExtreme and MAUI controls/components will work in our upcoming v21.2 beta. We expect to announce official support in November (once we officially release v21.2).

Though v21.2 beta 1 will not include .NET 6 support for Blazor, we expect to deliver .NET 6 support once Microsoft officially releases .NET 6.

Known .NET 6-related Issues (EAP and Beta 1 Builds)

Visual Studio Design Tooling does not support multiple unique (IDE-specific) design assemblies inside a single NuGet package. For this reason (and this reason alone), our DevExpress.Win.Design NuGet package does not offer design-time support for .NET 6 projects in Visual Studio 2022 (Preview/RC builds). While frustrating, a workaround exists: start and design a .NET 5 project in Visual Studio 2019 then rebuild the project with .NET 6.

11/10/2021: v21.2.3 (the Release build) fully supports Visual Studio 2022 Preview5/6. You can use the DevExpress.Win.Design package in both Visual Studios (2019 and 2022) to develop .NET 5 and .NET 6 projects.

Project Converter

Many of you are already familiar with our Project Converter – an indispensable tool for those converting from one major version of our product library to another. If you have never used our Project Converter and wish to learn more, please check out the following help topic: Project Converter.

We are currently working on a .NET Framework to .NET 6 Converter. At present, this new tool can convert standard WPF and WinForms projects to .NET 6, but we're hoping to extend it so you can leverage its capabilities (as a universal conversion tool) regardless of application type/target platform.

Visual Studio 2022 and .NET 6 Support for Older Versions

Our current focus remains on v21.2. We have yet to finalize Visual Studio 2022-related delivery plans for older builds (v21.1x or earlier). If we do offer a Visual Studio 2022-compatible version of an older build, we’ll announce it here.

11/10/2021: We currently have no plans to introduce the Visual Studio support in versions prior to v21.2.

Your Feedback Matters

As always, we welcome your feedback. If you’re using Visual Studio 2022/targeting .NET 6, we’d love to hear from you. Specifically, are you using Visual Studio 2022 for production code? Have you migrated existing solutions to .NET 6 (or begun a new .NET 6 project)? What framed your decision to migrate to .NET 6 and/or use Visual Studio 2022 prior to official release?

Free DevExpress Products – Get Your Copy Today

The following free DevExpress product offers remain available. Should you have any questions about the free offers below, please submit a ticket via the DevExpress Support Center at your convenience. We’ll be happy to follow-up.
dbSoft
dbSoft

Greate news!!

One question:  .NET Framework to .NET 6 Converter, will it include all the controls we have used so far in net framework?

As far as i understand, microsoft want to create one large framework for all projects. Example NET 6 will include winforms,wpf,maui, asp net and so on. (Correct me if i am wrong)


So we are looking fordward to upgrade are projects from .NET Framework to .NET 6. 

14 October 2021
Dmitry (DevExpress)
Dmitry (DevExpress)

@dbSoft our Project Converters do not replace the controls themselves, only update referenced project assemblies to their newer versions (or corresponding NuGet packages). So theoretically yes, all of your existing controls should be able to keep working. Certain specifics can apply (most obvious example, individual controls can have issues at design time), but the basic idea of course is to create a tool that will upgrade a project without a necessity to manually fix it afterward.


As for the second part, I'm afraid I don't fully understand the question. NET 6 is a global framework, yes, but MAUI, Win, and WPF projects are still separate types of projects.

14 October 2021
dbSoft
dbSoft
Thank you Dmitry for your quick response. What is the Devexpress opinion? Should we upgrade our Net Framework winforms projects to Net 6 winfroms? Or it is better to wait?
14 October 2021
Dmitry (DevExpress)
Dmitry (DevExpress)
@dbSoft Always a pleasure :) I'm not in any position to speak on behalf of the entire company, and it really depends on what you expect from this move (what benefits .NET Core brings to your specific project), but honestly, I believe you shouldn't hurry with the migration. You might have noticed one word being repeated A LOT in this pos — "preview". Visual Studio 2022 comes with a better .NET 6 support, and it is the in Preview/RC stage. NET 6 itself is also available as a preview version. So at the very least, I'd wait for stable versions. Once they are released, you could start weighing the pros and cons and planning the migration roadmap.
14 October 2021
Rajesh Aravapalli
Rajesh Aravapalli
@dmitry when can we expect Blazor components to support AOT?
14 October 2021
Peter Sørensen
Peter Sørensen

I have a production computer with both VS2019 and VS2022 installed.

I have to make sure my VS2019 stays as it it, without having 2 version of DevExpress components in its toolbox.

Can I install this beta in ONLY my VS2022 preview version ?

 
15 October 2021
Dmitry (DevExpress)
Dmitry (DevExpress)

@Peter: I don't think you can force our installers to ignore specific Visual Studio instances, but that should not be a major inconvenience: you can always manually remove unnecessary Toolbox components & DevExpress extensions after the installation. 


@Rajesh: I've passed your questions to our Blazor team, someone will post a reply shortly. Thank you.

15 October 2021
Peter Sørensen
Peter Sørensen
@dmitry I will suggest that you look at how JetBrains installer do it. I would love that your installers could make installations in the same way, in only the VS versions I want.
15 October 2021
Christopher Jay
Christopher Jay
I have tested the VS 2022 preview but am waiting for the final release before I start using it for actual daily programming and production code.  I am anxiously waiting for the final release and anticipate upgrading to it immediately, but not migrating past .NET 4.5.2 immediately.  Your updated project converter to .NET 6 will be fantastic for us when the time comes... thank you!  Thank you for your continued support of Winforms and support in general.
15 October 2021
Dmitry (DevExpress)
Dmitry (DevExpress)
Thank you for those words, Christopher. With WinForms - yes, we're not yet ready to dismiss this platform as outdated as it still has a lot to offer. Glad we're not the only devs who're feeling this way :)
15 October 2021
DÖNÜŞ ŞENEL
Dönüş ŞENEL
will winforms design time problems be solved in these new versions?
16 October 2021
Dmitry (DevExpress)
Dmitry (DevExpress)
@DÖNÜŞ Given that .NET API is constantly in flux, I can only promise that we'll certainly do everything possible to achieve that. 
18 October 2021
CRM-0c09a3d5-5491-481e-814b-ea6f4e089000
Christophe MOMMER

Hello,

I am using, since VS 2022 preview 2, using it for production projects, as it is stable enough and more performant than VS 2019 on larger projects.

Still, I have to keep VS 2019 installed for DevExpress' reports, among other things.

Hopefuly can get rid of VS 2019 soon !

18 October 2021
Vladimir Frizen (DevExpress)
Vladimir Frizen (DevExpress)
@Rajesh

Our Blazor components will support .NET 6 after its official release. At the same time, the AoT feature still works not so well as in simple scenarios. Our team is working on this issue, but we may need additional time to support this feature.

 

20 October 2021
CRM-12606e55-5a1b-422c-aab3-b0a0eb2371d2
John K

we need more Blazor client controls and keep the releases without many break change please.


thanks so much.

Devexpress forever.-

22 October 2021
Vladislav Kiselev
Vladislav Kiselev

We are not using VS anymore and have no plans to return back.

Is there anything on possible problems with Rider?

28 October 2021
CRM-49a54daa-6c16-4310-9f10-0ce9c7ea3f22
Lakra4k
I love DevExpress! <3
3 November 2021
Dmitry (DevExpress)
Dmitry (DevExpress)

@Vladislav AFAIR, DevExpress has never announced official support for any IDE that is not Visual Studio, so I'm afraid I'm not prepared to share any information regarding potential issues with Rider.


@Lakra4k thank you, this feeling is mutual :)

3 November 2021
CRM-d7a2b19f-0d5d-481c-bcfe-425339bed940
hdefu.com

For winform projects using vs2022 and dev18.1.5 to develop. NetFramework4.0 , this error will only be prompted when using the designer for the first time, and can be used normally later,As long as you don't use dev's designer


not found System.String EnvDTE._DTE.get_Version()

8 November 2021
Michael Paulus
Michael Paulus

Any update on blazor support for .net 6? 


I keep getting this error:
resource DevExpress.Blazor.v21.2.xml in DevExpress.Blazor.v21.2, Version=21.2.3.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a(4,10): error IL2008: Could not resolve type 'System.Threading.WasmRuntime'

9 November 2021
Dmitry (DevExpress)
Dmitry (DevExpress)
@hdefu.com as for now, we do not plan to support Visual Studio 2022 in versions prior to v21.2.
10 November 2021
Customer78699
Lior
When is V21.2.4 planned to be release? is V21.2.3 usable in the VS2022 released version?
10 November 2021
Customer78699
Lior
ok, just tested,  V21.2.3 is NOT usable in the VS2022 non preview version
10 November 2021
DÖNÜŞ ŞENEL
Dönüş ŞENEL
When opening the Devexpress project in vs2022, it appears as NET 6.0 Preview. When will the stable version be released?
 
10 November 2021
Vladimir Frizen (DevExpress)
Vladimir Frizen (DevExpress)

@Michael

Our Blazor components will support .NET 6 in the next v21.2.4 build. Currently, we are testing them with the final .NET 6 version. Could you please submit a ticket with steps to reproduce the mentioned error to our support center?

10 November 2021
Dmitry (DevExpress)
Dmitry (DevExpress)

@Lior Please report this issue to our Support Center, v21.2.3 should be working fine.

@DÖNÜŞ It's called ".Net 6 (Preview)" because at the time we released v21.2, neither stable .NET 6 nor Visual Studio 2022 were available. The "Preview" word should be gone in v21.2.4.

10 November 2021
Customer78699
Lior
@Dmitry, You are right, I was using older version. Thanks!
10 November 2021
Jim Lear
Jim Lear
I see lots of 2011 references in the blog.  Are these supposed to be 2021?
16 November 2021
Dmitry (DevExpress)
Dmitry (DevExpress)
@Jim Oops, thanks you for noticing this. Of course, these are 2021 updates.
16 November 2021
CRM-0d344203-78ad-47e6-87a9-b87ef7562ee8
Mario VH
We are starting a new project using Blazor Components, you said that "Our Blazor components will support .NET 6 in the next v21.2.4 build", but considering that .Net 5 support ends on May 08,2022, Is there any estimated release date of 21.2.4 build? 2021 or 2022?

Thanks!
17 November 2021
Dmitry (DevExpress)
Dmitry (DevExpress)
@Mario sorry for the late response. We expect to release v21.2.4 in early December.
23 November 2021
CRM-56aa3e5e-b233-4b24-bec0-66d46d755565
Customer119746

I updated my winforms 4.6 to use 21.2.3 in VS202 - it was working OK.

Then, after updating the application (using the "upgrade-assistant" from Microsoft) to .net 6 I started getting "The type or namespace name 'DevExpress' could not be found".


I tried fixing and reinstalling devexpress but didn't work.


Any idea?

best,

R.

23 November 2021
Mohammad Javad Tavakoli
Mohammad Javad Tavakoli
im upgarde my winfrom  project to net6 with vs2022 and devexpress 21.2.3 but i have problem with form designer ,this cant loading form design 
28 November 2021
Dmitry (DevExpress)
Dmitry (DevExpress)

@Customer119746 Try our Project Converter (Visual Studio Main Menu - DEVEXPRESS - WinForms Controls - Migrate the current project to .NET Core). If the issue persists, please submit a Support Center ticket.


@Mohammad it's hard to tell what the issue is based on one comment. If you face any technical issues, please submit a new Support Center ticket, our support engineers will do their best to help.

8 December 2021
CRM-63e8c410-c824-4c24-bb64-c4ecf59d0b97
Customer168885

i just install the new 21.2.4 and still having problems to create DevExtreme project in visual studio 2022, it seems that there's still incompatibility with VS 2022, the error message is :

one or more required DevExtreme files were not found. please run the installer to repair or reinstall  DevExtreme.

9 December 2021
Mick Devine_1
Mick Devine_1

DevExpress 21.2.4 XtraReport designer keep not working on Visual Studio 2022 with .Net 4.6.2.


Error: 

Could not load file or assembly 'Microsoft.VisualStudio.Shell, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Call Stack:

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at  Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)

10 December 2021
Lex (DevExpress Support)
Lex (DevExpress Support)

@Customer168885, thank you for your feedback. Usually, the error you received occurs when our wizard can't find files in the Program Files (x86)\DevExpress 21.2\DevExtreme folder. Thus, please check the following:

  1. Make sure that your antiviral tools do not block anything during the installation process and when you open the project.

  2. Make sure that you run Visual Studio and our installation with Administrator privileges.

  3. Make sure that all experimental features are disabled in Visual Studio 2022.

  4. Clear Visual Studio cache: How to clear visual studio cache.

  5. Make sure that all Visual Studio background processes are finished before you try to create a new application


If this does not help, please submit a ticket in our Support Centerand share the following information:

  1. Installation logs from this folder: C:\Program Files (x86)\DevExpress 21.2\DevExtreme
  2. Visual Studio Activity Log: Troubleshooting Extensions with the Activity Log.

We will do our best to find a precise solution for you.

14 December 2021
Dmitry Tok (DevExpress Support)
Dmitry Tokmachev (DevExpress)

@Mick Devine_1: Thank you for your feedback. We need a complete call stack and environment details to search for the issue cause (Visual Studio 2022 exact version from the About dialog, a list of installed extensions). Could you please collect all this info and create a new ticket under the Reporting category in the DevExpress Support Center: https://devexpress.com/ask?

 

14 December 2021
CRM-8bf58878-a72f-42af-8fc3-fb5e2e060d1b
Daniel

"Visual Studio Design Tooling does not support multiple unique (IDE-specific) design assemblies inside a single NuGet package. For this reason (and this reason alone), our DevExpress.Win.Design NuGet package does not offer design-time support for .NET 6 projects in Visual Studio 2022 (Preview/RC builds)."


Why not just have multiple packages for each design assembly and then have a meta package that pulls in all those individual packages. 

5 January 2022
CRM-8bf58878-a72f-42af-8fc3-fb5e2e060d1b
Daniel

"Visual Studio Design Tooling does not support multiple unique (IDE-specific) design assemblies inside a single NuGet package. For this reason (and this reason alone), our DevExpress.Win.Design NuGet package does not offer design-time support for .NET 6 projects in Visual Studio 2022 (Preview/RC builds)."


Why not just have multiple packages for each design assembly and then have a meta package that pulls in all those individual packages. 

5 January 2022
CRM-8bf58878-a72f-42af-8fc3-fb5e2e060d1b
Daniel

"Visual Studio Design Tooling does not support multiple unique (IDE-specific) design assemblies inside a single NuGet package. For this reason (and this reason alone), our DevExpress.Win.Design NuGet package does not offer design-time support for .NET 6 projects in Visual Studio 2022 (Preview/RC builds)."


Why not just have multiple packages for each design assembly and then have a meta package that pulls in all those individual packages. 

5 January 2022
CRM-8bf58878-a72f-42af-8fc3-fb5e2e060d1b
Daniel

"Visual Studio Design Tooling does not support multiple unique (IDE-specific) design assemblies inside a single NuGet package. For this reason (and this reason alone), our DevExpress.Win.Design NuGet package does not offer design-time support for .NET 6 projects in Visual Studio 2022 (Preview/RC builds)."


Why not just have multiple packages for each design assembly and then have a meta package that pulls in all those individual packages. 

5 January 2022
CRM-8bf58878-a72f-42af-8fc3-fb5e2e060d1b
Daniel

"Visual Studio Design Tooling does not support multiple unique (IDE-specific) design assemblies inside a single NuGet package. For this reason (and this reason alone), our DevExpress.Win.Design NuGet package does not offer design-time support for .NET 6 projects in Visual Studio 2022 (Preview/RC builds)."


Why not just have multiple packages for each design assembly and then have a meta package that pulls in all those individual packages. 

5 January 2022
CRM-8bf58878-a72f-42af-8fc3-fb5e2e060d1b
Daniel

"Visual Studio Design Tooling does not support multiple unique (IDE-specific) design assemblies inside a single NuGet package. For this reason (and this reason alone), our DevExpress.Win.Design NuGet package does not offer design-time support for .NET 6 projects in Visual Studio 2022 (Preview/RC builds)."


Why not just have multiple packages for each design assembly and then have a meta package that pulls in all those individual packages. 

5 January 2022
CRM-8bf58878-a72f-42af-8fc3-fb5e2e060d1b
Daniel

"Visual Studio Design Tooling does not support multiple unique (IDE-specific) design assemblies inside a single NuGet package. For this reason (and this reason alone), our DevExpress.Win.Design NuGet package does not offer design-time support for .NET 6 projects in Visual Studio 2022 (Preview/RC builds)."


Why not just have multiple packages for each design assembly and then have a meta package that pulls in all those individual packages. 

5 January 2022
CRM-8bf58878-a72f-42af-8fc3-fb5e2e060d1b
Daniel

"Visual Studio Design Tooling does not support multiple unique (IDE-specific) design assemblies inside a single NuGet package. For this reason (and this reason alone), our DevExpress.Win.Design NuGet package does not offer design-time support for .NET 6 projects in Visual Studio 2022 (Preview/RC builds)."


Why not just have multiple packages for each design assembly and then have a meta package that pulls in all those individual packages. 

5 January 2022
CRM-8bf58878-a72f-42af-8fc3-fb5e2e060d1b
Daniel

"Visual Studio Design Tooling does not support multiple unique (IDE-specific) design assemblies inside a single NuGet package. For this reason (and this reason alone), our DevExpress.Win.Design NuGet package does not offer design-time support for .NET 6 projects in Visual Studio 2022 (Preview/RC builds)."


Why not just have multiple packages for each design assembly and then have a meta package that pulls in all those individual packages. 

5 January 2022
CRM-8bf58878-a72f-42af-8fc3-fb5e2e060d1b
Daniel

"Visual Studio Design Tooling does not support multiple unique (IDE-specific) design assemblies inside a single NuGet package. For this reason (and this reason alone), our DevExpress.Win.Design NuGet package does not offer design-time support for .NET 6 projects in Visual Studio 2022 (Preview/RC builds)."


Why not just have multiple packages for each design assembly and then have a meta package that pulls in all those individual packages. 

5 January 2022
CRM-8bf58878-a72f-42af-8fc3-fb5e2e060d1b
Daniel

"Visual Studio Design Tooling does not support multiple unique (IDE-specific) design assemblies inside a single NuGet package. For this reason (and this reason alone), our DevExpress.Win.Design NuGet package does not offer design-time support for .NET 6 projects in Visual Studio 2022 (Preview/RC builds)."


Why not just have multiple packages for each design assembly and then have a meta package that pulls in all those individual packages. 

5 January 2022
CRM-a5b4c5a7-6ba3-43da-894d-1bdfd67b1a9b
Erik

Are there any news on the project converter to convert .NET framework apps to .NET 6/7? Is it still in development? I am really looking forward to something like this, considering that I have a lot of .NET framework apps that I would eventually like to migrate.


Kind regards

Erik

11 August 2022

Please login or register to post comments.