C#

Luc Pattyn wrote:

I did not intend to suggest to permanently put an if(DesignerMode)return; in the code;
my intention was just to help pinpoint where exactly things start to go wrong,
expecting that info would point to the real problem, and hopefully the real solution.

Luc Pattyn wrote:

In general, I would try not to add if statements at all: the more of them, the harder it
gets to test all cases, and to understand what goes wrong when things starts to fail...

using System.ComponentModel;
 
PropertyDescriptorCollection pdcMyControl = TypeDescriptor.GetProperties(MyControl);
 
foreach(PropertyDescriptor pdMyControl in pdcMyControl)
{
    System.Type  pd_typ = pdMyControl.PropertyType.GetInterface("ICollection");
    if (pd_typ != null) 
    {
	ICollection ItemsMyControl = pdMyControl.GetValue(MyControl) as ICollection;
	foreach (object obj in ItemsMyControl)
	{
            //Maybe a recursion needed here!
            //...
        }
    }
    else
    {
	//pdMyControl.GetValue(MyControl)); //returns object
    }
}

• To get all the properties of a type, use the Type.GetProperties() method. Pass in the following binding flags: Instance, Public, FlattenHierarchy. This makes sure that only public members that are instance rather than static are returned, and that inherited properties are included.

• To get the data type of a property use the PropertyInfo.PropertyType method.
• A simple way to see if a property's type is one of the basic types is to check if Convert.GetTypeCode!=TypeCode.Object.
• Watch out for circular reference paths! Check each time before you output an object's properties to make sure that the object isn't already currently being output.
• A property value may be part of a large object graph, and outputting the whole graph as text could bring the app to its knees. Consider limiting the recursion depth.