Thanks again Diego.
It is a framework but the main issues I'm having is when I have an
interface that (e.g.) restricts properties to getters but the concrete
class has an internal setter to allow controller methods to hook
things together. These controller methods take in an interface but
need to cast to the concrete to access a setter.....
e.g.
AddComponent(IThing item)
{
((Thing).item).Parent = this;
}
I also have a base class that overrides the comparer for equality
checks, but proxies do not inherit from this base class so the
comparer fails to return true for something like
_collection.Contains(item).... as item is a proxy that is not in the
_collection but it's matching concrete type is.
I don't think these are edge case scenarios (and any comments are
welcome)
tbh, I'm coming to the conclusion that nice as proxies from an
interface are, they are more trouble than they are worth.
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en.
