No, this is by design.
Using encrypted duplex TCP channel within the same AppDomain makes no sense.
Please use another protocol for the in-process communication.
You can start several ZyanComponentHost instances with different protocols — one for IPC, another for duplex TCP.
Both component hosts can share the same ComponentCatalog, so ipc host publishes the same components as tcp host:
Using encrypted duplex TCP channel within the same AppDomain makes no sense.
Please use another protocol for the in-process communication.
You can start several ZyanComponentHost instances with different protocols — one for IPC, another for duplex TCP.
Both component hosts can share the same ComponentCatalog, so ipc host publishes the same components as tcp host:
var tcpProtocol = new TcpDuplexServerProtocolSetup (port, employeeService, true); var tcpHost = new ZyanComponentHost ("ITJH", tcpProtocol); // for remote connectionsvar ipcProtocol = new IpcBinaryServerProtocolSetup("AnyPortName"); var ipcHost = new ZyanComponentHost("ITJHIpc", ipcProtocol, tcpHost.ComponentCatalog); // for local machine connections
