why is the reflection of an class not cached?

Nov 8, 2006 at 3:31 PM
The PropertyReflectionStrategy looks up the properties that need to be filled and fills them.
but the information, what it should fill in an class never changes, since it is defined by the attributes of the properties.

why is there no type caching, so you get by BuilderContext and type the cached list of things to do (e.g. IParameter's).

i think this could improve the performance, since there is much reflection and also (as i'm using it) the CreateParameter of an ParameterAttribute could do some preprocessing depending on the return type.
Coordinator
Nov 8, 2006 at 3:47 PM
You are right. Caching would certainly help perf and is pretty easy to implement. We know of many projects that have created a customized strategy for this.