Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Context.RegisterDynamicProperty Method

This method supports the .NET Framework infrastructure and is not intended to be used directly from your code.

Registers a dynamic property implementing the IDynamicProperty interface with the remoting service.

Namespace: System.Runtime.Remoting.Contexts
Assembly: mscorlib (in mscorlib.dll)

public static bool RegisterDynamicProperty (
	IDynamicProperty prop,
	ContextBoundObject obj,
	Context ctx
)
public static boolean RegisterDynamicProperty (
	IDynamicProperty prop, 
	ContextBoundObject obj, 
	Context ctx
)
public static function RegisterDynamicProperty (
	prop : IDynamicProperty, 
	obj : ContextBoundObject, 
	ctx : Context
) : boolean

Parameters

prop

The dynamic property to register.

obj

The object/proxy for which the property is registered.

ctx

The context for which the property is registered.

Return Value

true if the property was successfully registered; otherwise, false.

Exception typeCondition

ArgumentNullException

Either prop or its name is a null reference (Nothing in Visual Basic), or it is not dynamic (it does not implement IDynamicProperty).

ArgumentException

Both an object as well as a context are specified (both obj and ctx are not a null reference (Nothing in Visual Basic)).

Based on obj and ctx, prop is asked to contribute a sink that is placed at some location in the path of remoting calls. If multiple properties are registered, their sinks will be called in an arbitrary order that can change between calls.

If obj is not a null reference (Nothing in Visual Basic), and then if it is a proxy, all calls made on the proxy are intercepted. Otherwise, if obj is a real object, all calls on the object are intercepted. The ctx parameter must be a null reference (Nothing in Visual Basic).

If ctx is not a null reference (Nothing in Visual Basic), obj must be a null reference (Nothing in Visual Basic) and all calls entering and leaving the context are intercepted.

If both ctx and obj are a null reference (Nothing in Visual Basic), all calls entering and leaving all contexts are intercepted.

Windows 98, Windows 2000 SP4, Windows Millennium Edition, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see System Requirements.

.NET Framework

Supported in: 2.0, 1.1, 1.0

Community Additions

ADD
Show:
© 2015 Microsoft