LoaderOptimization.MultiDomain Explanation

  • Thread starter Thread starter BuddyWork
  • Start date Start date
B

BuddyWork

Hello,

Can some explain how the CLR decides on which assembly will be shared
across domains. The explaination in MSDN is not enough.
From MSDN:
Click to expand...
Indicates that the application will probably have many domains that use
the same code, and the loader must share maximal internal resources
across application domains.

Thanks,
 
Hello,

As I see it - if you plan your application to have multiple application
domains, and you plan to load the assembly in question to many of those
domains (say, the assembly contains widely used utility functions), you
should set this flag.
 
Thanks for the reply,

I want to know how it decides what is shared across domains. For example
does the whole assembly get shared by comparing the code, or does it
compare the assembly version or does it share objects within the
assembly.

Thanks,
 
Search for the "Drill Into .NET Framework Internals to See How the CLR
Creates Runtime Objects" article in MSDN magazine archives (May 2005 issue).
It appears to shed some light on this.
 
Back
Top