You menitioned in "\DOCS-SDKs\sdk_adapter_dotnet\examples\Remote_StockListD emo_Adapters\Deployment\Deployment_LS(robust)\Stoc kList_sockets\adapters.xml":

+ RobustNetworkedMetadataProvider: "Moreover, this Metadata Adapter manages the case in which the remote counterpart is missing, by just refusing all new requests from the clients and storing all state change notifications that have to be sent to the backend (namely, session closing and table closing notifications). Meanwhile, this Metadata Adapter keeps waiting for a connection from a new remote server; upon connection, it will flush pending notifications, then start working normally."

+ RobustNetworkedDataProvider: "This Data Adapter also manages failures of the remote counterpart, by waiting for connection from a new remote server and trying to recover the data flow."

I don't know how Remote .NET Adapter Server, Remote .NET Metadata Adapter, and Remote .NET Data Adapter work together with those "robust" proxies in case of failure? What is proper way to implement Server's ExceptionHandler to recover failure?

I read in "DOCS-SDKs\sdk_adapter_dotnet\examples\Remote_Portfolio_ Adapters\src_standalone_launcher\StandaloneAdapter sLauncher.cs", you noted that:
        // Notes about exception handling.        
        // In case of exception, the whole Remote Server process instance
        // can no longer be used;
        // closing it also ensures that the Proxy Adapter closes
        // (thus causing Lightstreamer Server to close)
        // or recovers by accepting connections from a new Remote
        // Server process instance.
        // Keeping the process instance alive and replacing the Server
        // class instances would be possible.
        // This would issue new connections with Lightstreamer Server.
        // However, new instances of the Remote Adapters would also be needed
        // and a cleanup of the current instances should be performed,
        // by invoking them directly through a custom method.
It is very good if you can provide completed example for failure recovery at remote server side.