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.
--
Sincerely,
Dmytro Lapshyn [Visual Developer - Visual C# MVP]
"BuddyWork" <dh*****@bankofny.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...
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:
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,