J
Jack Wright
Dear All,
Every Virtual directory under IIS is executed in a new AppDomain.
This is done by CLR itself. When I deploy a dll under its bin, the
AppDomain is restarted as a result all my dlls under the bin again go
for compilation.
Is there anyway to avoid this? Can I create a AppDomain
programatically, that will avoid this error? Will putting the dll in
GAC solve the problem?
How do I avoid AppDomain restarts under IIS due to hot deployment?
Also if my application access any function of a dll, then it does not
get copied into the bin folder (message stating that the dll is in use
is displayed). How do I overcome these? Please help...
Thanks & Regards
Jack
Every Virtual directory under IIS is executed in a new AppDomain.
This is done by CLR itself. When I deploy a dll under its bin, the
AppDomain is restarted as a result all my dlls under the bin again go
for compilation.
Is there anyway to avoid this? Can I create a AppDomain
programatically, that will avoid this error? Will putting the dll in
GAC solve the problem?
How do I avoid AppDomain restarts under IIS due to hot deployment?
Also if my application access any function of a dll, then it does not
get copied into the bin folder (message stating that the dll is in use
is displayed). How do I overcome these? Please help...
Thanks & Regards
Jack