BuyLog In
Bug Report T1047452
Visible to All Users

Core - Visual Studio 2022 is unsupported in XAF / XPO v21.2.3 (ORM Data Model Designer, Model Editor and Solution Wizard)

created 3 years ago (modified 3 years ago)

Plans

We will support XPO's ORM Data Model Designer, XAF's Model Editor and Solution Wizard for Visual Studio 2022 in v21.2.4 (early December 2021). For more information about other products, please review Visual Studio 2022 and .NET 6 Support | Current Versions, Supported IDEs, Version History.

Please follow our team blogs for updates: XPO Team Blog, XAF Team Blog.

Workaround

XAF/XPO: In the meantime, please use Visual Studio 2019.
XPO: Use the CodeRush | XPO Templates to create XPO classes with a few keystrokes.

Search keywords

VS2022, VS 2022, DevExpress Template Gallery Failed: Method not found: 'EnvDTE.Solution EnvDTE.get_Solution()'

Sign in to comment on this post

Answers approved by DevExpress Support

created 3 years ago (modified 3 years ago)

We have addressed the issue described in this ticket and will include a fix in our next maintenance update. Should you need to apply our fix prior to official release, you can request a hotfix here.

Important Notes:

  • Hotfixes may be unavailable for Early Access/Beta builds or updates set for release within a week.
  • .NET only: in the NuGet Package Manager, use your personal NuGet feed and check the "Include prerelease" option to view the hotfix package in the "Updates" tab.
Additional information:

Good news! XPO's ORM Data Model Designer, XAF's Model Editor, and Solution Wizard support Visual Studio 2022 in v21.2.4.
We hope to release a compatible build within a week or so.

To test this before the official release and share your feedback with the XAF team, please download and run the hot-fix installer (NuGet is insufficient for design-time fixes like this one).

Important Notes

  1. The latest Visual Studio Modeling SDK has an issue that affects a few menu commands of XPO's ORM Data Model Designer (Add new external Type, Add new persistent object, Add new user comment). Please comment and vote for this issue to inform Microsoft of its importance for you, if necessary: https://developercommunity.visualstudio.com/t/domain-specific-language-designer-dsl-explorer-con/1603273.
    UPDATE: This issue is fixed in version 17.1.0 Preview 2.0 of Visual Studio.
  2. Since Visual Studio 2022 is a 64-bit application, XAF's Model Editor does not work with projects that target x86 in the build configuration. Please specify the Any CPU platform (Build | Configuration Manager).
  3. Our Model Editor still uses the .NET 5.0 version. You can get the "To run this application, you must install .NET" exception in cases when you do not have the required .NET 5.0 environment. Please refer to the following ticket for details and recommendations: Core - Model Editor does not work with .NET 6 projects.
    You can also use Dave Hesketh's approach from the following thread: XAF ModelEditor - To run the application please install .NET.
    If these workarounds do not help, please create a new ticket and attach the %USERPROFILE%\AppData\Roaming\eXpressAppFramework folder.
  4. Beware of the following known issues in v21.2.4:
  1. The new v21.2.4 build and Visual Studio 2022 change nothing about XAF's Controller/Action design-time functionality - it is no longer available in XAF's .NET 5+ apps. We recommend that you create XAF's Controllers/Actions in code with a few keystrokes using CodeRush templates.
  2. As you may recall from our roadmap, we also will NOT support the Module and Application Designers in .NET 5+ apps (.NET Framework apps will be unaffected), because they mostly duplicate the Solution Wizard functionality and are rarely used (occasional module or application configurations can be easily accomplished with a few lines of code: example). To have easy and consistent configurations for security and application modules across WinForms and Blazor in .NET+, XAF v22.1 will support Dependency Injection (DI) extensions like in ASP.NET Core Blazor Server apps.

@For ALL who intend to leave a comment in this thread ticket:
This ticket is being tracked by many customers and we want to avoid confusion and misinformation, if possible. If something does not work for you with the update, please choose to submit a separate ticket using the https://devexpress.com/ask service. To allow us to help you faster, be sure to attach screenshots of errors, callstacks, Solution Explorer, NuGet Package Manager, Error List and other supporting information. Thank you for your understanding.

Thanks,
Dennis
Product Manager
dennis@devexpress.com

    Show previous comments (2)
    M M
    Martin Praxmarer - DevExpress MVP 3 years ago

      "To have easy and consistent configurations for security and application modules across WinForms and Blazor in .NET+, XAF v22.1 will support Dependency Injection (DI) extensions like in ASP.NET Core Blazor Server apps."

      That sounds impressive :)

      FB FB
      Franco Bonacchi 3 years ago

        @Dennis i've installed 21.2.4 and i can't open the model editor, nor see the Update Model contextual menu items on the solution. I'm using VS2022 and i expected 21.2.4 will just work with it as the release notes said? I'm using .NET Framework XAF solution. Cheers!

        Dennis Garavsky (DevExpress) 3 years ago

          @Franco Bonacchi: I answered you in a separate ticket: T1052401: Model Editor and the Update Model command are unavailable in XAF's v21.2.4 for .NET Framework apps in Visual Studio 2022 - I am happy to hear that it is working now (after updating packages from v21.2.3 to v21.2.4).

          @For ALL who intend to leave a comment in this thread ticket:
          This ticket is being tracked by many customers and we want to avoid confusion and misinformation, if possible. If something does not work for you with the update, please choose to submit a separate ticket using the https://devexpress.com/ask service. To allow us to help you faster, be sure to attach screenshots of errors, callstacks, Solution Explorer, NuGet Package Manager, Error List and other supporting information. Thank you for your understanding.

          Sign in to comment on this post

          Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

          Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.