Why isnt ContextBoundObject an interface?

[Brian Takita]

Hello,

I was looking at the ContextBoundObject implementation and saw that this

class does nothing more than call the MarshalByRefObject's constructor
in its constructor.

That tells me that ContextBoundObject is some sort of marker that tells
the rest of the framework that the class that inherits it has a bound
context.

Unfortunately, c# only has single inheritance, which means you can't
inherit from a class and get the benefits of a ContextBoundObject.

Wouldn't an interface be a better choice? It would allow you to inherit
from another class while using ContextBinding.

Is this a "design choice" to force the developer to use aggregration if
she wants to use build upon a class that was not meant to be ContextBound?

Thank you,
Brian Takita

 

[Mattias Sjögren]

Brian,

Wouldn't an interface be a better choice? It would allow you to inherit
from another class while using ContextBinding.

Is this a "design choice" to force the developer to use aggregration if
she wants to use build upon a class that was not meant to be ContextBound?

I suspect the reason is the same as why MBRO isn't an interface, which
is discussed here.

http://blogs.gotdotnet.com/cbrumme/PermaLink.aspx/c11743c6-29c9-416f-a403-f4fdebb24366



Mattias