Hi,
When setting CanContentScroll style to True, it will enable UI Virtualization. Only the displayed cells will be loaded. By default, the DataGrid uses virtualization for columns and rows. You don't have to change anything.
In the case of a statically declared table, if this is the source of the DataGrid and virtualization is enabled, virtualization will act on it and not load everything, only the displayed cells.
You should always use virtualization with maybe the exception of really small datasources.
Instead of adding/removing columns, why not just playing with their visibility ? It is less costly.
In the full version of the DataGrid, you a batch update which consist of doing actions on columns and then update the visual only once. This really increases the performance. You can test this in the Full Datagrid demo here : http://xceed.com/Grid_WPF_Demo.html. Look for the last sample : "and more.../batch Updating". In this sample, you can add/remove 300 columns in a normal way (around 10 seconds) or add/remove 300 columns with batch updating (around 0.5 second). But if you only need to do actions on 1 or 2 columns at a time, the batch update won't be that useful. It is interesting for actions on many columns and then to only do 1 refresh.
The Extended WPF Toolkit only contains 1 grid, which is a downgraded version of the Full Xceed WPF Datagrid. So if you need to display columns of data, I believe you need a grid, not another control from the Extended WPF Toolkit.
When setting CanContentScroll style to True, it will enable UI Virtualization. Only the displayed cells will be loaded. By default, the DataGrid uses virtualization for columns and rows. You don't have to change anything.
In the case of a statically declared table, if this is the source of the DataGrid and virtualization is enabled, virtualization will act on it and not load everything, only the displayed cells.
You should always use virtualization with maybe the exception of really small datasources.
Instead of adding/removing columns, why not just playing with their visibility ? It is less costly.
In the full version of the DataGrid, you a batch update which consist of doing actions on columns and then update the visual only once. This really increases the performance. You can test this in the Full Datagrid demo here : http://xceed.com/Grid_WPF_Demo.html. Look for the last sample : "and more.../batch Updating". In this sample, you can add/remove 300 columns in a normal way (around 10 seconds) or add/remove 300 columns with batch updating (around 0.5 second). But if you only need to do actions on 1 or 2 columns at a time, the batch update won't be that useful. It is interesting for actions on many columns and then to only do 1 refresh.
The Extended WPF Toolkit only contains 1 grid, which is a downgraded version of the Full Xceed WPF Datagrid. So if you need to display columns of data, I believe you need a grid, not another control from the Extended WPF Toolkit.