Since Q2 2010 all major changes for the controls are listed in the official Release Notes posted here

RadInputManager textboxes will by default have no CSS class if the Skin is set to an empty string (no skin). This ensures interoperability with RadFormDecorator, which only decorates textboxes with no CSS class. When using RadInputManager with custom CSS classes and no Skin, it is recommended to set all state CSS classes for the InputSettings, instead of just one or two - EnabledCssClass, HoveredCssClass, FocusedCssClass, InvalidCssClass, EmptyMessageCssClass, ReadOnlyCssClass, DisabledCssClass (or at least all CSS classes for states that will be used).

In order to decorate RadInputManager textboxes with RadFormDecorator, set Skin="" and EnableEmbeddedBaseStylesheet="false" to the RadInputManager control.

Removed obsolete client API methods from the code:

RadInput for ASP.NET AJAX which is part of the Q2 2009 release is fully backwards compatible with its previous version (Q1 2009).

The RadInput skins has been improved and and the css classes/images used in them were unified with the rest of RadControls for ASP.NET AJAX. If you intend to use the old versions of the skins to avoid layout changes/skins updates, you can find the entire set of old skins (prior to the Q1 2009 release) attached to this forum post.

They have been adapted to be fully compatible with the Q1 2009 release. In order to use them as non embedded skins, you should do the following:

1. copy the corresponding CSS file and images to your website, the exact location depends on your preference;

2. register the CSS file manually with a <link> tag or via an ASP.NET theme;

3. set EnableEmbeddedSkins="false" to the control, which will use the non-embedded skin;

For more information about RadControls' skinning mechanism and using non-embedded skins, please refer to:

How skins work

Skin registration

Using skins in ASP.NET themes

Disabling embedded resources

An online demo, which shows how to use various RadControls with non-embedded skins is available at: Custom skins demo

All CSS classes for RadInput and RadInputManager have been renamed to use Telerik's current CSS naming convention. As a result, all RadInput skins have decreased in size by up to 25%.

All custom skins will stop working, however, migrating is very easy, by following the CSS selector scheme provided below:

Caution

Please note that the list above shows how the CSS classes have changed, but it is not a direct indication about how the CSS selectors should be constructed - this is a matter of preference and generally, you should follow your current scheme. However, since the new CSS classes do not have a skin suffix, you will need to add the CSS class of the control's wrapper (.RadInput_Skin) to each selector. For example: (old selector) .radHoverCss_Skin {...} (new selector) .RadInput_Skin .riHover {...}

RadInputManager styles:

RadInputMgr_Skin (common CSS class)

RadInput_Empty_Skin

RadInput_Enabled_Skin

RadInput_Hover_Skin

RadInput_Focused_Skin

RadInput_Disabled_Skin

RadInput_Negative_Skin

RadInput_Error_Skin