Materializing objects inheriting from DynamicObject

A few days ago I found myself in the need to use Query<T> with an object inheriting from DynamicObject.

Currently, as per @mgravell's kind answer, this is not supported. He suggested I open an issue so you guys can take a look.

All references to my use case are detailed in my StackOverflow question linked above, along with a brief and by no means complete exchange of opinions as to how this could be handled.

Basically, the constructor for DefaultTypeMap (going from memory here, the names could be wrong) is quite PropertyInfo-centric, which would probably need to to be changed to also look at T and whether it implements IDynamicMetaObjectProvider.

The suggestions were to support DynamicObject-derived objects both for materializing and as parameters, hence:

• probing for IDynamicMetaObjectProvider
• allowing use of such objects as parameters, with the limitation that they have to provide an override for GetDynamicMemberNames()

Start with the DefaultTypeMap constructor and its PropertyInfo-centric lookup, then trace the materialization and parameter paths for types implementing IDynamicMetaObjectProvider. Done means DynamicObject-derived types are supported for materialization and parameters, with parameter objects requiring GetDynamicMemberNames() as described.