marshaler

The former is accomplished using some form of serialization engine, or marshaler. The latter is achieved through some form of metadata.

Provides a way for clients to access the actual object, rather than the adapter object handed out by a custom marshaler.

The marshaler identifies the object by looking at one of the interfaces the object implements.

When a string is passed by value, the callee must never alter the reference passed by the marshaler.

When the interface is first passed through the marshaler, the marshaler checks whether the interface is coming from a known object.

When arrays are passed as C-style arrays, the marshaler cannot determine the size of the array.

The interop marshaler performs the identical transformation when exposing a VARIANT type to managed code.

Best-fit mapping enables the interop marshaler to provide a close-matching character when no exact match exists.

Provides access to the underlying object wrapped by a custom marshaler.

If either attribute is omitted, the marshaler can optimize by eliminating either copy.

You apply them to method parameters when you want to alter the default behavior of the marshaler.

The marshaler pins data to reduce the overhead of copying and enhance performance.

Describes the process for writing a custom marshaler for interoperation.

The marshaler can use the CLSID to locate the metadata for the wrapper.

By using a custom marshaler, you can minimize the distinction between new .

Before you can build a marshaler, you must define the managed and unmanaged interfaces being marshaled.

For example, the marshaler determines that the class wrapper should be used to wrap the interface that was passed into managed code.