JetBrains.Rider.DotNetIpc.Protocol ==ADVERTISE PROTOCOL== Before standard IPC Protocol communication can occur on a client-mode connection the runtime must advertise itself over the connection. ALL SUBSEQUENT COMMUNICATION IS STANDARD DIAGNOSTICS IPC PROTOCOL COMMUNICATION. The flow for Advertise is a one-way burst of 34 bytes consisting of 8 bytes - "ADVR_V1\0" (ASCII chars + null byte) 16 bytes - CLR Instance Cookie (little-endian) 8 bytes - PID (little-endian) 2 bytes - future

Errors (HRESULT) returned for DiagnosticsServerCommandId.Error responses.

Different diagnostic message types that are handled by the runtime.

Initiates core dump generation

Starts an EventPipe session that writes events to a file when the session is stopped or the application exits.

Stops an EventPipe session.

Starts an EventPipe session that sends events out-of-proc through IPC.

Attaches a profiler to an existing process

Message header used to send commands to the .NET Core runtime through IPC.

Request type.

Remote process Id.