.NET Core 3.0+
.NET Framework 4.5.2+
.NET Standard 2.0+
.NET Core 3.0+

XafApplication.OptimizedControllersCreation Property

Disables the instantiation of Controllers that will never be activated in nested List Views.

Namespace: DevExpress.ExpressApp

Assembly: DevExpress.ExpressApp.v20.2.dll


public bool OptimizedControllersCreation { get; set; }
Public Property OptimizedControllersCreation As Boolean

Property Value

Type Description

true, if the optimized controllers creation is enabled; otherwise, false.


When the OptimizedControllersCreation property is set to true, View Controllers that won't be activated due to ViewController.TargetViewType, ViewController.TargetViewNesting, ViewController.TargetObjectType or ViewController.TargetViewIdrestrictions are not created.

This optimization is supported in Windows and Frames, whose Frame.View is not changed during the Frame life cycle:

If you have a custom Action which changes the Frame's View (e.g, by setting TargetWindow to Current) in one of the aforementioned cases, set OptimizedControllersCreation to false.

The OptimizedControllersCreation value has no effect when the Frame's View can be changed (e.g., when the Frame is the application's main window). In this case, all Frame's Controllers are instantiated preliminarily.

In applications created using the Solution Wizard version 17.1 or higher, the OptimizedControllersCreation property is set to true by default. It is recommended to set it to true in applications that are created in older versions. This can be done in the WinApplication and WebApplication descendant's constructors:

public partial class MainDemoWinApplication : WinApplication {
    public MainDemoWinApplication() {
        this.OptimizedControllersCreation = true;
    // ...

To avoid possible null reference exceptions when accessing an existing Controller from your code, always ensure that the Frame.GetController<ControllerType> method result is not null when the XafApplication.OptimizedControllersCreation property is true.

See Also