ICustomTypeDescriptor defect

2 posts, 0 answers
  1. Vladimir
    Vladimir avatar
    11 posts
    Member since:
    Oct 2010

    Posted 08 May 2014 Link to this post


    Symptoms: RadDataForm don not see custom properties of object which implements ICustomTypeDescriptor when RadDataForm.CurrentItem set and RadDataForm.ItemsSource is null.

    Location ItemPropertyInfoHelper.cs(Telerik.Windows.Data.dll assembly Telerik.Windows.Data namespace):
    private static PropertyDescriptorCollection GetPropertyDescriptors(QueryableCollectionView collectionView)
    if (TypeExtensions.IsCompatibleWith(elementType, typeof (ICustomTypeDescriptor))) //code pass
            return ItemPropertyInfoHelper.GetPropertyDescriptorsForCustomTypeDescriptorElementType(collectionView);
    public static PropertyDescriptorCollection GetPropertyDescriptorsForCustomTypeDescriptorElementType(QueryableCollectionView collectionView)
          var customTypeDescriptor = ItemPropertyInfoHelper.GetCollectionViewRepresentativeItem(collectionView) as ICustomTypeDescriptor; //returns null
          if (customTypeDescriptor != null) return customTypeDescriptor.GetProperties(); //Never called when ItemsSource is not set
          else return null;
    private static object GetCollectionViewRepresentativeItem(QueryableCollectionView collectionView)
          if (!collectionView.IsEmpty) return collectionView.GetItemAt(0); //collection is empty
          else return null;

    Can you confirm this behavior?
    Telerik version 2013.3.1016.40

  2. Maya
    Maya avatar
    4062 posts

    Posted 12 May 2014 Link to this post

    Hello Vladimir,

    Indeed, you are right. I have logged the issue in our Portal so that you can follow its progress. 
    Thank you for reporting this, I updated your Telerik points accordingly. 

    Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.
Back to Top