This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I am using the new GetValue<T> and SetValue<T> constructs. However, GetValue<T> has class type constraint on the TField, but SetValue<T> has no constraints at all. Is this by design? Thanks again, Kavan |
|
|
Hi Kavan, This is by design. GetValue is only intended for lazy value object fields which should normally be a class type like string, byte[] or Address etc. Cheers, Andrew. |
|
|
Hi Andrew, Is there any downside to lazy loading integers and the such. Say I have a class with sixty or seventy propertys of which fifty are hardly ever used. I would like to decorate those fifty props with an EagerLoad attribute, so as to group them as logical load unit. Looking at the lazy load code, it really looks like just an arbritary restriction, not one which is an implementation issue. Thanks always, Kavan |
|
|
Hi Kavan, I'll remove the constraint. Cheers, Andrew. |
|