tunic wrote:
Is this a bug however, as perhaps it shouldn't be checking properties that can't be mapped to as they are hidden?
In reality, You can not actually "hide" the property - it will remain accessible from code.
And from lazy loading point of view, the fact wether proeprty is mapped or not is unimportant. Code behind public instance method/property might (and propably does) access the persitent state of object, directly or indirectly. So the object should be initialized before any public method is executed. And for that, the member must be virtual.
Gert