Limitations in WPF Spreadsheet (SfSpreadsheet)

27 Feb 20251 minute to read

Release memory held by AutomationPeer

SfSpreadsheet holds some instance in memory even after disposing the spreadsheet or removed the sheets from the spreadsheet. Because, the AutomationPeer for WPF Components holds some memory and it needs to be released manually. This can be done by using the following steps.

Create a class derived from WindowAutomationPeer and override it’s GetChildrenCore method and returns “null” value that clears the AutomationPeer item from memory as follows

C#

public class FakeWindowsPeer : WindowAutomationPeer
{

    public FakeWindowsPeer (Window window): base(window)
    { }

    protected override List<AutomationPeer> GetChildrenCore()
    {
        return null;
    }
}

Now override the OnCreateAutomationPeer of the window and it returns the class as follows.

C#

public partial class MainWindow : Window
{

    public MainWindow()
    {
        InitializeComponent();
    }

    protected override AutomationPeer OnCreateAutomationPeer()
    {
        return new FakeWindowsPeer(this);
    }
}

NOTE

You can refer to our WPF Spreadsheet feature tour page for its groundbreaking feature representations. You can also explore our WPF Spreadsheet example to know how to render and configure the spreadsheet.