Problems while migrating from 2009 to 2012 Dlls

2 posts, 0 answers
  1. Jeff Lishingman
    Jeff Lishingman avatar
    18 posts
    Member since:
    Oct 2009

    Posted 26 Apr 2012 Link to this post

     

    Hi,

    Recently we have upgraded from 2009 to 2012 Telerik Rad Controls dlls (Silverlight 4). We need few clarifications regarding the changes done in Rad Expander and RadGrid:

     

    1. In Rad Expander, for 2012 TemplateDown,TemplateUp,TemplateLeft,TemplateRight are obsolete, Can you tell us what are the alternate ways for this properties?

     

    http://www.telerik.com/help/silverlight/changes-backward-compatibility.html following link only provides the changes, but not the information/details on the alternate methods.

     

    2. In 2009 ColumnFilterDescriptor used to have a FieldFilterDescriptor. FilterDescriptor.Member attribute. But in 2012 ColumnFilterDescriptor is changed to IColumnFilterDescriptor and FilterDescriptor to IFieldFilterDescriptor. We are not able to understand how to get this "Member" attribute on "OperatorValueFilterDescriptorBase". Can you please suggest us how this can be done?

     

    Thanks,
    Sripriya

  2. Petar Mladenov
    Admin
    Petar Mladenov avatar
    3152 posts

    Posted 01 May 2012 Link to this post

    Hi Jeff,

    1.There are no analogical properties in the RadExpander in Q1 2012. We refactored its template in 2011, you can see the new template structure here. However, you can send us your custom styles and we will help you to upgrade them.

    2. Here you can find the list of breaking changes regarding filtering. We had to make them because we implemented filtering for our expression column which has no notion of Member. That is why we extracted all common logic for the two kinds of columns to the base abstract class OperatorValueFilterDescriptorBase.

    Assuming that your column is a GridViewDataColumn, you have to different ways to get the Member.

    A) Since this is an IColumnFilterDescriptor, you have a reference to the column so you can get Column.DataMemberBinding.Path.Path.

    B) In case your column is a normal GridViewDataColumn (i.e. which has a DataMemberBinding), you can safely cast the abstract OperatorValueFilterDescriptorBase to a FilterDescriptor which has a Member.

    In case your column is a GridViewExpressionColumn, you can safely cast the OperatorValueFilterDescriptorBase to a LambdaFilterDescriptor which has a LambdaExpression instead of a Member.

    Long story short, we extracted everything except for the Member property from the FilterDescriptor class up to the base abstract OperatorValueFilterDescriptorBase class so that the new LambdaFilterDescriptor can derive from it and reuse its code. 

    We hope this helps.

    Kind regards,
    Petar Mladenov
    the Telerik team

    Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>

Back to Top