Pattern advice needed - How to avoid code duplication when separate Web and WinUi Controllers are needed?

Hello Andrew,
As you need to customize the Grid control, it's possible to create a base Controller class in the main module of your application, which will contain common code and some abstract methods. Then create two child Controller classes in the Web and Win module with platform-specific code.
You can do this in the following manner:
Base Controller class:

C#
public abstract class GridControllerCore : ViewController {  
     protected override void OnActivated() {  
         View.SelectionChanged += View_SelectionChanged;  
     }  
     protected abstract void SetupGrid(); // method for platform specific grid customization  
     // common code  
 }  

And its child is in the Win module:

C#
public class WinGridController : GridControllerCore {  
    protected void SetupGrid() {  
        GridListEditor gridListEditor = ((ListView)View).Editor as GridListEditor;  
        if(gridListEditor == null) { return; }  

        gridView = gridListEditor.GridView;  
        gridView.OptionsBehavior.EditorShowMode = EditorShowMode.MouseUp;  

        gridView.OptionsSelection.ShowCheckBoxSelectorInGroupRow = DevExpress.Utils.DefaultBoolean.True;  
        gridView.OptionsView.ShowButtonMode = DevExpress.XtraGrid.Views.Base.ShowButtonModeEnum.ShowAlways;  

        gridView.OptionsSelection.MultiSelectMode = GridMultiSelectMode.CheckBoxRowSelect;  

        gridListEditor.Grid.HandleCreated += Grid_HandleCreated;  
    }  
}  

Thanks Sergey
So I guess there is not a single platform agnostic controller then … shucks

Hello Andrew,
Controls are different for each platform and it is not possible to completely avoid writing platform-dependent code in this particular case.
However, it is possible to implement a more reusable solution through Application Model extensions that will enable a developer to set options within a platform-agnostic module. In its turn, there will still be two platform-dependent Controllers that will map platform-agnostic model options to the actual control properties. This way many standard XAF and third-party modules are implemented.

Welcome, Andrew.