I've just been switching to NHibernate 1.2.0 from 1.0.4 and have discovered that some of the class members I had mapped as "protected internal" to provide internal access to members but also support proxying are now reported as illegal mappings.

Does anyone know if this is this intentional or a bug?

Symon.

Yes, it's intentional because internal actually has the same risks as public - if an internal field is accessed before the proxy is initialized, you get an incorrect value.

Thanks Sergey.