Hi,

I'd like to understand the point of not allowing internal fields and if possible a proposed alternative.

The background: I'm injecting dependencies through some internal fields and the IInterceptor, but fields cannot be virtual. Must I always create a virtual setter method? Is there a pattern advising against doing it this way? Is there a better way to do it?

http://jira.nhibernate.org/browse/NH-988

Thanks
Cristian

It's the same as with public fields - if you access them directly and the object is a proxy, you will never get correct values, not even after the object is initialized.

BTW current implementation of ProxyTypeValidator is incomplete - it handle just one "special case" - Object.GetType, but there are more if one will inherit persistent classes from MarshalByRefObject...
At least this members cause errors:
IsInstanceOfType, GetComIUnknown, CanCastToXmlType, InvokeMember, __RaceSetServerIdentity and __ResetServerIdentity

We can of course modify the proxy validator to take this into account, but why are you inheriting persistent objects from MarshalByRefObject? It seems to me a strange thing to do. And are you sure that the methods you mentioned will behave correctly for proxies?

Thank you for quick reply, I'l try to convince colleagues that they really don't have to pass references to persistent objects via remoting.
BTW I don't know (and have no time and knowledge to make test) if .NET proxy will work with DynamicProxy, I personally don't use remoting in this case.