DomainAssembly represented an assembly loaded (or being loaded) into a particular app domain - that is, there was a unique DomainAssembly per assembly per app domain. In our one app domain world, DomainAssembly versus Assembly is a confusing abstraction. We should move things off of DomainAssembly and eventually remove it.
Some things it currently handles:
Exposed managed object for Assembly and Module - should be able to move to Assembly/Module
Associated with AssemblyObject - can probably become Assembly
FileLoadLevel, incremental loading based on level, and associated tracking/checks - maybe this - just load tracking - is what it becomes (renamed) or maybe collapse into Assembly
DomainAssembly
represented an assembly loaded (or being loaded) into a particular app domain - that is, there was a uniqueDomainAssembly
per assembly per app domain. In our one app domain world,DomainAssembly
versusAssembly
is a confusing abstraction. We should move things off ofDomainAssembly
and eventually remove it.Some things it currently handles:
Assembly
andModule
- should be able to move toAssembly
/Module
AssemblyObject
- can probably becomeAssembly
FileLoadLevel
, incremental loading based on level, and associated tracking/checks - maybe this - just load tracking - is what it becomes (renamed) or maybe collapse intoAssembly