>I am trying to build a web application (ASP.NET) which uses a DLL (created with V. FoxPro 7). The problem is that after running the application the DLL does NOT get released. I can only release it by resetting the IIS service.
>I would like to see the DLLHOST.EXE release my COM-DLL as soon as it is no longer in use.
>
>I have tried everything (object = Nothing, Marshal.ReleaseComObject(), etc..). I'm even wondering if this behaviour is normal with .NET, but I still need to know if that's the case. I have consulted in a number of books but nowhere do they mention this kind of problem.
>
>Does anyone know how I can solve this problem? I would be very greatful.
>Thanks in advance!



IIS uses object pooling. We had this problem and the only way I have seen is to restart IIS. You might want to look for a setting somewhere that disables that feature.