PropertyGrid and Dynamic Proxies with CustomTypeDescriptor

Hi,

we tried using your PropertyGrid with some dynamically generated proxy-classes and it seems that not everything behaves as we expected.

The scenario is a little more complex, so I cannot provide a full sample, but I try to explain it:

There is a "normal" object of some class T, which is normally readonly.

When we need it to be editable, we use LinFu (http://code.google.com/p/linfu/) to generate an editable proxy-class at runtime, which implements basically the same interfaces as the original object, but now with working implementations of the property-setters.
LinFu cares for that every method call on the proxy is intercepted and directed to the right implementation.

Both classes use the same CustomTypeDescriptor, which works nice when retrieving properties via
var x = TypeDescriptor.GetProperties(proxyObject.GetType()); or other access-methods via TypeDescriptor.

However, using this proxy in the PropertyGrid does strange things:

• Converters are not properly treated for some properties
• Setting a bool-property via a TypeEditor did not set this property-value, but instead triggered other actions in the object (all of its properties have been set to their actual value, which caused exceptions in our case, because not all properties are allowed to be set.
• other (standard) editors also did not work, changing the value for an enum Property for example made the error-template appear.

Looking at your source-code I got the impression that the PropertyGrid/ObjectWrapper uses Type.GetProperty("propName") and not the TypeDescriptor, which might lead to different results.

Is there any way, how I can control the PropertyGrid, i.e. its way of reflecting object-properties?

Or can you tell me, how I must customize my class/proxy to make it compliant to the PropertyGrid?
Obviously I don't want to create a custom type editor for each possible datatype of any property.

We use PropertyDescriptors where possible (for normal properties); as far as I know we use PropertyInfo only for indexed properties (which PropertyDescriptor doesn't support).  Certainly we have people using ICustomTypeDescriptor successfully on their objects.

I appreciate that your real scenario is quite complex, but would it be possible for you to create a cut-down repro with just one or two sample classes and their proxies, so that we can investigate this and make any required fixes?  Thanks!

Sounds like our scenario should "normally" just work.

Maybe it' something completely different.
I will try to reproduce it in a less complex sample.

Problem solved: 

While trying to reproduce the problem, I found and fixed a bug in one of our PropertyDescriptors (ComponentType returned PropertyType), since then the problem has disappeared.

Thanks for your help.