Hello,

Instead of Modules i want my assembly subparts to behave as plugins, load/unload on runtime without affecting host app. Can you guide me how this is possible with this library, currently i am using DotnetCorePlugins
but this have bug in razor that your library solves, so i am interested if i can port to yours.

thanks

modularization mains:

1. cold module load
2. module can call each other
3. module may cause host app crash
4. module is static for the app
5. module may need isolation ( data and service isolation, not Type/Assembly isolation )

plugin mains:

1. cold plugin load
2. cold plugin unload
3. hot plugin load
4. hot plugin unload
5. must need Type/Assembly isolation
6. plugin may need to call each other
7. plugin may need to modify the parent plugin host app.
8. plugin must not cause host app crash! (the plugin itself can crash)
9. plugin is dynamic for the app

problems

1. hot plugin unload is limited (emit stuff can not be used)
2. assembly isolation is hard : while we need some framework type in the plugin's host app (a framework type may not in the host app or a framework.extensions type is inside a plugin too [consider of , self-contained, different runtime (desktop runtime, server runtime and .net 6 introduce an assembly missing that is System.Drawing.Common) ])
3. Plugin call each other has the same problem like problem 2
4. A type shared across host app and plugin , then it can not be isolated to it's child plugin.

目前已经支持常规的asp.net core 3.x 的网站加载（即，采用默认的DI和没有动态代理的网站， autofac 再不支持动态代理的情况下，理论上是支持的）

已知问题：

1. 动态代理不支持 可卸载 Alc
2. 根据 Abp的测试，Abp采用的动态Controller/Endpoint 也会出现问题
3. 目前的实现不支持热插拔， 在下个版本中，将采用中间件方式重新映射子应用路径， 到时候将支持热插拔
4. asp.net core 程序集必须加载到AssemblyLoadContext.Default 里面去, 这里应该是 alc 的设计问题， 目前正在提交新的issue