Yes it a dutch name. You are correct, if domain object gets complicated, reflection is not sufficient. I use it for very simple objects (poco).

Yes, it works just fine with the forms designer.

Your implementation is slightly different, you are generating the display objects on the fly based on a domain object. I am instantiating my display class based on the type passed in. Basically, you made a simple scaffold. How does this work with lookups? Also, I’m dealing with more complicated edit logic (plus custom edit controls).

As far as using generics on the display class: That is correct, but that would only be beneficial if you were dealing with common controls, and then you would lose the true generic-ism of the form, that code would be tied to implementations.

It would be better if you had your display controls inherit from a common base class, and bind the generic to that base class instead of the one I showed.

Or, if you have a case with only one control needing custom behavior: create a controller class that creates the generic form and grabs a reference to the control, then the controller class can implement the custom behavior. At most you would only have to expose one or two new properties to make that happen.

I guess I just don’t like using reflection unless I absolutely have to.