>Can someone do this test for me?
>
>If you have an ASP.NET application, could you upload a new copy of the DLL at the same time a hit is in progress? I have a situation that sometimes the DLL is updated, but IIS cannot load it back in memory. Thus, a iisreset /restart is necessary. This is very annoying as it causes this situation for all Web sites that sit on the server. So far, the busier the site, the more chances that a hit in progress will occur, and that will cause this reaction.
>
>I haven't been able to simulate that on several servers but one. So, it has to be something in my configuration. Also, based on previous threads, many have confirmed that they never have this situation. So, it has to be done on this side. But, just to be sure, if someone can launch a hit on a Web server that will last for about 20 seconds for example, the time it would take for the upload of the DLL to replace the existing one, that would be a test I would be curious to know if the IIS server hangs out or if it is able to grab the new DLL as is.
>
>As, this is a very serious problem I am trying to resolve. If I send a new DLL, I need to find a way to make sure that I will never have to do a iisreset /reset, thus avoiding a reset on all other Web sites. But, as I said, this happens on specific occasions only. It is not all the time.


You could isolate each web site in its own app pool. The app pool might recycle when you upload a new DLL, but the other web sites would be ok.