Richard, Thanks again for answering, i should create a new improvement ticket in jira. But still i want someone to think about the consequence of the Lazy property proxy not being able to proxy internal classes, is this behavior expected and wanted, or is it not a use case.
I can imagine people using internal domain objects to shield some implementation details from the outside. If it is not a use case, then in my oppinion, we need to throw an exception when the class is not public (remember that it works perfectly if we not use lazy properties on string, byte[] etc). a quickfix is either adapt the example test NH0000 to using public classes or use InternalsVisibleTo (in the test assembly == untested ;)) Kind regards
