XAF v22.1 marks the official release of our Code & Project Diagnostics (5 more popular XAF diagnostics are added as well). Previously, we added these error diagnostics only to new v21.2 projects by default (using the DevExpress.Express.CodeAnalysis NuGet package). With v22.1.4 (the next minor after the official release v22.1.3) we want to enable our Code & Project Diagnostics in existing XAF projects using the Project Converter automatically. For more information, review https://docs.devexpress.com/eXpressAppFramework/403389/debugging-testing-and-error-handling/code-diagnostics.
Motivation:
- help our customers improve overall app quality/performance;
- avoid resource drain due to bad practices in custom code, because dealing with their consequences takes time from customers and also DevExpress support representatives.
We are choosing between adding Code & Project Diagnostics to XAF projects unconditionally OR offering an opt-out screen in the Project Converter. What do you think about this change in general and what are your preferred options to enable this feature?
@domsinclair nice to hear - thanks for your opinion. BTW, today I had a customer who hit 3 of errors that could be detected by our built-in diagnostics in one ticket, which also affected the normal behavior of his app. Auto-fixes is a part of my long-term vision for this thing - for now we need to beef it up (20 more diagnostics are on our TODO list).
I shared our thoughts on the future of our XPO ORM Data Model Designer in https://supportcenter.devexpress.com/ticket/details/t1084770/moving-a-table-in-xpo-diagram-causes-visual-studio-2022-to-hang
Thank you for sharing. Unfortunately, this is not the first and last time in the history of the XPO ORM Data Model Designer when we are dependent on the behavior of the Microsoft Modeling SDK (DSL tools, the design surface, panels, etc.), which is outside of our control.
Having carefully analyzed the team efforts to support new Visual Studio versions and react to breaking changes in the IDE architecture (extension loading, .NET Core, etc.), we are considering dropping the XPO ORM Data Model Designer support with v22.2. Another reason is the low performance of the tooling when dozens of classes with dozens of properties are displayed in the diagram.
We want to recommend the Code-First approach to our customers instead. To generate persistent classes from an existing database, we want to provide a console tool or Item Template/Wizard as it is now.
What do you think about this?
You can see what to expect from XAF v22.1 in https://community.devexpress.com/blogs/xaf/archive/2022/02/28/xaf-2022-roadmap-cross-platform-net-app-ui-and-api-services.aspx (I updated it 3-4 weeks ago after a code freeze). Let me know if you have any questions on the upcoming capabilities.
I have a couple of projects still using xaf webform and waiting for a better UI experience/functionality (detailview and grid) before updating
I hope you will like v22.2 enhancements to the list and detail view: https://www.devexpress.com/subscriptions/new-2022-2.xml#xaf
@dengara_gitlab will popups be resizable in 22.2? And what about notifications module?
Blazor popups are resizeable in code from v22.1: https://docs.devexpress.com/eXpressAppFramework/404014/ui-construction/templates/in-blazor/change-popup-window-dimensions?v=22.2. We had no Scheduler/Notifications in our v22.2 roadmap: https://community.devexpress.com/blogs/xaf/archive/2022/08/03/xaf-enhanced-navigation-and-grid-in-blazor-audit-trail-and-download-reports-media-data-in-web-api-v22-2.aspx