This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

// A context-agile object is loaded into context 0.

class SportsCar{}

On the other hand, objects that do demand contextual allocation are termed context-bound

objects, and they must derive from the System.ContextBoundObject base class. This base class solidi-

fies the fact that the object in question can function appropriately only within the context in which

it was created. Given the role of .NET context, it should stand to reason that if a context-bound

object were to somehow end up in an incompatible context, bad things would be guaranteed to

occur at the most inopportune times.

In addition to deriving from System.ContextBoundObject, a context-sensitive type will also be

adorned by a special category of .NET attributes termed (not surprisingly) 

context attributes. All

context attributes derive from the ContextAttribute base class, which is defined within the System.

Runtime.Remoting.Contexts namespace:

public class ContextAttribute :

Attribute, IContextAttribute, IContextProperty

{

public ContextAttribute(string name);

public string Name { virtual get; }

public object TypeId { virtual get; }

public virtual bool Equals(object o);

public virtual void Freeze(System.Runtime.Remoting.Contexts.Context newContext);

public virtual int GetHashCode();

public virtual void GetPropertiesForNewContext(

System.Runtime.Remoting.Activation.IConstructionCallMessage ctorMsg);

public Type GetType();

public virtual bool IsContextOK(

A Single .NET Process