Design guidelines on Application Domain using C#

[wycklk]

Suppose:

Process 1 contains: AppDomain A, AppDomain B
Process 2 contains: AppDomain C

Is there any design guidelines on partitioning the
AppDomain (for example, I should put AppDomain C within
Process 1 instead of Process 2 for better performance vs
stability etc) ?

Next, is .NET remoting the only way for AppDomain A to
communicate with AppDomain B and C ? Is there a
performance gain for .NET remoting if AppDomain A and
AppDomain B are located within the same process ?

 

[Rajeev Goel]

I'm no expert, but I'm almost certain that cross-process calls are more
expensive than cross-AppDomain calls within the same process. One of the
reasons for inventing AppDomains is that it's way to provide some isolation
for part of your application that is cheaper than creating a whole separate
process.

You should only create a separate AppDomain (within the same process) if
you truly need the isolation it provides.

--Rajeev
Visual Studio .NET
Microsoft Corp.

This posting is provided "AS IS" with no warranties, and confers no rights.