Log In
Home
Support
Demos
Documentation
Blogs
Training
Webinars
[Expand]General Information
[Collapse]WinForms Controls
  Prerequisites
 [Expand]What's Installed
 [Expand]Build an Application
 [Expand]Controls and Libraries
 [Collapse]Common Features
  [Expand]Data Binding Common Concepts
  [Expand]Data Source Wizard
  [Expand]Expressions
  [Expand]Behaviors
  [Expand]Application Appearance
  [Expand]Filtering UI Context
  [Expand]High DPI Support
  [Expand]Scaffolding Wizard
  [Expand]Formatting Values
   HTML Text Formatting
  [Expand]Menus
  [Expand]Tooltip Management
  [Expand]Saving and Restoring Layouts
   Clipboard - Copy Data and Formatting
   Version Compatibility: Default Property Values
  Get More Help
 [Expand]API Reference
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Document Server
[Expand]Reporting
[Expand]Report Server
[Expand]Dashboard
[Expand]eXpressApp Framework
[Expand]CodeRush
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

Version Compatibility: Default Property Values

The latest DevExpress installation introduces new features that may drastically change the default behavior of particular controls. When you migrate to the newest version of DevExpress controls and components, you have an option to revert these features to the previous version by utilizing the static WindowsFormsSettings.DefaultSettingsCompatibilityMode property.

All the newest changes are in effect if the WindowsFormsSettings.DefaultSettingsCompatibilityMode property equals Latest.

Expanded Version 16

The table below illustrates what properties may act differently if you set the WindowsFormsSettings.DefaultSettingsCompatibilityMode property to v16 (when compared to the Latest mode).

Control
Affected properties
Description
GridControl
TreeList
VGridControl
ColumnViewOptionsBehavior.UnboundColumnExpressionEditorMode
TreeListOptionsBehavior.UnboundColumnExpressionEditorMode
VGridOptionsBehavior.UnboundColumnExpressionEditorMode
End-users invoke the standard Expression Editor dialog instead of the newest dialog that supports auto-completion and syntax highlighting.
GridControl
TreeList
XlsExportOptionsEx.GroupState
XlsxExportOptionsEx.GroupState
Legacy behavior (v16): In Data-Aware Export Mode (when the XlsExportOptionsEx.ExportType / XlsxExportOptionsEx.ExportType property equals DataAware), the XlsExportOptionsEx.GroupState and XlsxExportOptionsEx.GroupState properties do not depend on the current GridOptionsPrint.ExpandAllGroups and TreeListOptionsPrint.PrintAllNodes property values. GroupState properties are by default set to Default, and groups within an exported Excel document are expanded or collapsed depending on their current state within a Data Grid or Tree List.

New behavior (Latest): In Data-Aware Export Mode, if the GridOptionsPrint.ExpandAllGroups and TreeListOptionsPrint.PrintAllNodes properties equal true, the XlsExportOptionsEx.GroupState and XlsxExportOptionsEx.GroupState properties' Default value is equivalent to ExpandAll. Otherwise, the Default setting checks the current group (node) state within a control (same as in legacy behavior).
GridControl
TreeList
GridOptionsFilter.AllowAutoFilterConditionChange
OptionsColumnFilter.AutoFilterCondition
TreeListOptionsFilter.AllowAutoFilterConditionChange
TreeListOptionsColumnFilter.AutoFilterCondition
Legacy behavior (v16): end-users cannot modify filtering conditions when utilizing the Data Grid and TreeList automatic filtering rows. As a developer, you can manually select the desired condition by utilizing the OptionsFilter.AutoFilterCondition property for a Data Grid or Tree List column.

New behavior (Latest): automatic filtering rows for Data Grid and TreeList control display buttons that allow end-users to change the filtering expression operator. End-users are limited to a certain pool of conditions, depending on the column data type and filter mode (the GridColumn.FilterMode and TreeListColumn.FilterMode properties). For instance, by default end-users cannot select conditions like "Begins with..." for numeric columns.

The same limitations apply to developers. If you switch the OptionsFilter.AutoFilterCondition option to BeginsWith for a numeric column, it has no effect unless you change this column's filtering mode to DisplayText.
GridControl GridOptionsView.BestFitMode Best fit operations prefer calculation precision rather than speed.
GridControl GridOptionsCustomization.AllowMergedGrouping Grouping by multiple columns at once is disabled.
TreeList TreeListOptionsFind.AllowFindPanel Find panel is not available by default, the Ctrl+F shortcut does not invoke this panel.
TreeList TreeListOptionsBehavior.EnableFiltering By default, filtering in Tree List is disabled.
TreeList TreeListOptionsFilter.FilterMode The Default filter mode is equal to FilterMode.Standard instead of FilterMode.Extended.
PropertyGridControl PropertyGridControl.AutoGenerateRows Rows do not generate automatically.
GridControl
TreeList
OptionsColumnFilter.FilterPopupMode
TreeListOptionsColumnFilter.FilterPopupMode
Controls display standard filter dropdown menus instead of Excel-styled ones.
GridControl
TreeList
OptionsColumnFilter.ShowEmptyDateFilter
TreeListOptionsColumnFilter.ShowEmptyDateFilter
In Excel-styled filter dropdowns, the "Show Empty" items are hidden.
RibbonControl RibbonControl.RibbonStyle The Default style applies the RibbonControlStyle.Office2007 style rather than RibbonControlStyle.Office2013.
RibbonControl RibbonControl.TransparentEditorsMode Focused CheckEdit, RadioGroup and TrackBarControl in-place editors do not have a transparent background.
DevExpress Forms none Legacy behavior (v16): to enable form title bar skinning, you need to manually call the SkinManager.EnableFormSkins method before the form is created.

New behavior (Latest): the SkinManager.EnableFormSkins method is called automatically and you need to call the SkinManager.DisableFormSkins method to revert it back.

How would you rate this topic?​​​​​​​