Home/ Questions/Q 298945
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T06:46:40+00:00

I realize a rational knee-jerk response would be Remoting you idiot! Read the MSDN

  • 0

I realize a rational knee-jerk response would be “Remoting you idiot! Read the MSDN docs.” Every scrap of info I can find concerning .Net Remoting is in the context of inter-process communication: sockets, shared memory, pipes…the classics when it comes to IPC, but an AppDomain is not really a process. However, AppDomains seem to enjoy most of the benefits of being one. From an academic perspective, OS IPC primitives are heavy compared to communication between entities that reside in the same process. Is there a special AppDomain pipe that is used when communication crosses an AppDomain boundary within the same process? I doubt it. I would be shocked if MS changed the fundamentals of process isolation within the Windows kernel to accommodate AppDomains.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There’s a fast path in this case. There is no need for interprocess communication, since the appdomains live in the same process and the CLR has full access to all of them and the full address space. It’s really just some markers in the call stack for security and exception handling purposes as well as the unloadability that appdomains give.

    • 0