Guys, please help me with NuGet Hotfixes (thank you to those who already replied me via email).
If you are unsure about our plans, please see my post: https://community.devexpress.com/blogs/news/archive/2021/09/28/nuget-stability-and-authentication-enhancements-hot-fixes-portable-pdb-support-for-windows-and-linux-net-core-desktop-installer-deprecation.aspx
Based on our current understanding of customer needs, we do not plan to store hotfixes indefinitely, because hotfixes are not recommended for production and are temporarily used (we already have a ton of disclaimers for this).
We plan to store hot fixes either within a major (and remove them later after a new major is issued) or store just 10-15 the latest hotfixes within the major (and remove them after the limit).
My concern that NuGet.org does not remove hotfixes at all, and in theory, there may be a customer who leaves his CI on a hot fix and this CI will be broken when a new major or removal limit is reached. For me, this is not a bad thing (because a more stable version is available and it is not good to stay on unstable hotfixes long), but some may disagree.
What do you think of our plans to remove hotfixes from NuGet after some time?
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.
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?
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?