G
Guru Prasad
Is there a delay involved in unloading assemblies once a virtual directory
is "deleted" using IIS Manager ? At times even after the virtual directory
is removed i cannot delete the backing physical directory and it looks like
ASPNET runtime is holding on to the assemblies. Once i recycle the ASPNET
process, i can delete this directory. Has this got anything to do with
strong-named/signed assemblies ( even though deployed as private
assemblies ) ? Or is the loading/unloading behavior different for assemblies
that are used for HttpModules.
And is there a fix ?
is "deleted" using IIS Manager ? At times even after the virtual directory
is removed i cannot delete the backing physical directory and it looks like
ASPNET runtime is holding on to the assemblies. Once i recycle the ASPNET
process, i can delete this directory. Has this got anything to do with
strong-named/signed assemblies ( even though deployed as private
assemblies ) ? Or is the loading/unloading behavior different for assemblies
that are used for HttpModules.
And is there a fix ?