Breaking Changes in v2009 vol 2.10

This page lists important behavior and API changes, which were introduced in this version. If you already have projects using DXperience, you will need to peruse this list in order to understand the changes you might need to make to your source code to support this new release.

Note that we only publish the changes to the public interface of our controls. We reserve the right to change the protected, internal, or private interfaces when needed.

Table of Contents

• All ASP.NET Components
• ASPxGridView and Editors Suite
• ASPxHtmlEditor
• eXpressApp Framework

All ASP.NET Components

• BC470: The Loading Panel's content is separated into an image and text to best support its localization (within the Aqua, RedWine and SoftPrange themes).

ASPxGridView and Editors Suite

• BC450: Application of the ASPxEdit.IsValid property's value set via code has been corrected

  Now, if an editor is validated using a custom validation, that is, its IsValid property is set manually via code, editor validation (initiated via a call to its Validation method) affects the IsValid property's value in the following manner:
  
  1. If an editor's built-in validation is used (that is, the validation settings are defined via the ValidationSettings properties or within handlers of the client or server Validation event):
  
  1.1. If the editor's value is recognized as valid during editor validation, the IsValid property is set to True.
  1.2. If the editor's value is recognized as invalid during editor validation, the IsValid property is set to False.
  
  2. If an editor's built-in validation is not used (that is neither server or client Validation event is not handled, the ValidationSettings.RequiredField.IsRequired property is not set to True and the ValidationSettings.RegularExpression.ValidationExpression property is not defined), the IsValid property setting is preserved as it was before editor validation.
  
  Previously, if the built-in validation was not used (item 2) and an editor's IsValid property was set to False via code, then this property might be occasionally reset to True after calling editor validation.
  
  The related bug fixes:
  Q232954
  B142644

ASPxHtmlEditor

• BC422: ASPxHtmlEditor - A dynamically created custom toolbar button's default view style has been changed

  Previously, if a button of the CustomToolbarButton type was created by using a constructor with three parameters - CustomToolbarButton(string text, string name, string toolTip) - then, the created button's ViewStyle property was set to ViewStyle.Image by default.
  It meant that the text defined in the constructor wasn't visible by default, and an image object was expected to be assigned to the button's Image.Url property.
  
  Now, after fixing issue B141725, the ViewStyle property of a dynamically created button is always set to ViewStyle.Text regardless of the used constructor overload.
  If this change affects your project, you can modify the ViewStyle property of your created CustomToolbarButton object according to your requirements.

eXpressApp Framework

• BC455: Localization - PagesText, AllPagesText and LoadingPanelText localization items of ASPxGridView are now obsolete.

  The DevExpress.ASPxGridView control's PagesText, AllPagesText and LoadingPanelText localization items were removed from the Application Mode. Use the DevExpress.ASPxExperience's following items instead:
  
  Pager_SummaryFormat,
  Pager_SummaryAllPagesFormat,
  Loading.

• BC434: NavigationLinksActionContainer - Links are no longer created for inactive Action Items.