Notifies the profiler that a remoting call has run to completion on the client.
If the remoting call was synchronous, it has also run to completion on the server. If the remoting call was asynchronous, a reply might still be expected when the call is handled. If a reply is expected, it will occur as a call to ICorProfilerCallback::RemotingClientReceivingReply and an additional call to RemotingClientInvocationFinished to indicate the required secondary processing of an asynchronous call.
Each of the following pairs of callbacks will occur on the same thread:
RemotingClientInvocationStarted and ICorProfilerCallback::RemotingClientSendingMessage
You should be aware of the following issues with the remoting callbacks:
Execution of a remoting function is not reflected by the profiler API, so notifications for functions that are called from the client and executed on the server are not properly received. The actual invocation happens via a proxy object; to the profiler, it appears that certain functions are JIT-compiled but never used.
The profiler does not receive accurate notifications for asynchronous remoting events.
Platforms: See .NET Framework System Requirements.
Header: CorProf.idl, CorProf.h
.NET Framework Versions: 4, 3.5 SP1, 3.5, 3.0 SP1, 3.0, 2.0 SP1, 2.0