Reference vs. Value: Types, Passing and Marshalling

re: Reference vs. Value: Types, Passing and Marshalling

JackG — Wed, 25 Jan 2006 00:56:59 GMT

Great post.
I'm not sure I follow your statement "Contracts must be implemented on reference types that derive from MarshalByRefObject. The actual type of the class that implements the contract is not visible across the domain (and really should have no other public surface besides the contract), only the contract is visible, but nonetheless the class must derive from MarshalByRefObject in order to Marshal by Reference".
Could you restate this?
It seems contrary that the Contract impl. must derive from MBRO, but the type of the class is not visible accross the AD. Given the PDC05 sample of
public abstract class MenuBase : MarshalByRefObject, IMenuItemContract
this statement seems to imply that MenuBase is not visible in the Addin AD.

AppDomain's and Addin's

Jack Gudenkauf (JackG) WebLog — Sat, 11 Mar 2006 01:41:10 GMT

What is an Application Domain (AD)?
An Application Domain is a CLR feature that provides a unit of isolation...

AppDomains and Addins

Jack Gudenkauf (JackG) WebLog — Tue, 06 Nov 2007 14:21:35 GMT

What is an Application Domain (AD)? An Application Domain is a CLR feature that provides a unit of isolation

Extensibility; Clients and Services calling each other

Jack Gudenkauf (JackG) WebLog — Mon, 10 Mar 2008 23:33:07 GMT

In this post I will be showing sample code (also found on our CodePlex site ) as well as an execution

Customization Automation Addins and Life Reference vs Value Types | internet marketing tools

Tue, 16 Jun 2009 07:42:54 GMT

PingBack from http://einternetmarketingtools.info/story.php?id=22263