
The XAF team has officially confirmed a major architectural milestone: starting with XAF v25.2, support for .NET Framework applications is fully discontinued, and several legacy APIs, modules, and subsystems have been removed from the framework’s source code.
If you have XAF applications in production — especially those based on WinForms (.NET Framework) or ASP.NET WebForms — this is a critical shift to understand. This article breaks down what changed, why it changed, the impact, and how to migrate forward successfully.
Continue reading