My current project (a desktop application that’s currently developed on .net
v1.1) call for
1) Use ngen.exe to improve the startup speed.
2) Use multiple AppDomain to reduce the memory requirement. The idea is some
of the modules in the application are quite large and users could be working
on multiple modules during a single application session. We would like to
unload the modules they are finished. Each module will be loaded in a
separate AppDomain, and the AppDomain will get unloaded when the module is
finished.
We are having some problems trying to get both approaches working at the
same time. What we have been experiencing is that the assemblies that are
loaded into a new application domain will not use the ngen image (we know for
sure that the assemblies are ngen, and if we load it in a single AppDomain
scenario, the ngen image will be used)
Also, there is also a great article
(http://blogs.msdn.com/junfeng/archiv...14/429210.aspx) that I came
across which mention Domain Neutrality. Having a domain neutral AppDomain
will not help in our scenario, because assemblies will not be unloaded until
the process exit.
Has anyone come across this or know if there is a solution to this problem?
Thanks in advance!
