Unable to delete dir even after unload/remove ...

[Guru Prasad]

Does ASPNET process hold onto the app dir even after the app is "unload"ed
and "removed" ( via IIS manager ) ?
I am unable to delete a dir which was formerly a basedir for a webapp, until
i restart aspnet process. Why is this so ?

This makes things complicated during uninstall of a web application, since
killing aspnet is highly undesirable and may interfere with other apps.

Is this the normal IIS/ASPNET behavior ? What do i need to configure to
prevent IIS/ASPNET from doing so ?

Does the fact that i use strong-named assemblies ( still loaded from the
private bin path and not from the GAC ) make any difference to the
loading/unloading process ?

[Ken Cox [Microsoft MVP]]

Sometimes it is hard to release the IIS's grip on a component. This usually
works:

net stop iisadmin /y

Trouble is, it stops your Web site.

Perhaps an email to [email]mswish@microsoft.com?subject=ASP.NET[/email]

would help for the future?

Ken


"Guru Prasad" <gprasad@amberpoint.com> wrote in message
news:eNRMAEjUDHA.2184@TK2MSFTNGP10.phx.gbl...
Does ASPNET process hold onto the app dir even after the app is "unload"ed
and "removed" ( via IIS manager ) ?
I am unable to delete a dir which was formerly a basedir for a webapp, until
i restart aspnet process. Why is this so ?

This makes things complicated during uninstall of a web application, since
killing aspnet is highly undesirable and may interfere with other apps.

Is this the normal IIS/ASPNET behavior ? What do i need to configure to
prevent IIS/ASPNET from doing so ?

Does the fact that i use strong-named assemblies ( still loaded from the
private bin path and not from the GAC ) make any difference to the
loading/unloading process ?