I have created a dll that I am using via ASP pages. The problem that I run into is that, after running any page that accesses that dll, I am no longer able to re-compile the dll (I get the "Permission denied" error). Evidently the ASP server is grabbing that dll and holding it in memory, making it impossible to write over it during the re-compile. Is there a simple way of getting around this (i.e. flushing out some type of dll cache)? Thanks.

Jay