>>I just tested a little on a server here. Changes published to the web server immediately showed up even when just refreshing an existing page on the browser.
>>
>>How are you placing the DLL on the server and how are you checking that the update has kicked in?
>
>I have a Bin directory for each site. This is where the application DLL is stored. I also have Framework.dll, which is my .NET framework. I upload using my FTP application. This application uploads into a temporary directory. At the end, it just moves the file into the production directory. Then, on the next hit, the refresh of the DLL takes place. This usually takes about 10 seconds. But, when that happens, sometimes, it will stay in wait more forever and no response is send back to the browser. So, I have to do a iisreset /restart to have it back.

I normally just use the .NET publishing wizard but that shouldn't make any difference. As I understand it ASP.NET makes a shadow copy of the /bin directory and uses this shadow copy to service requests. It also monitors the actual /bin folder for any file changes therein. When it detects a change it builds a new shadow copy. The existing copy is still used to service existing requests. New requests use the new shadow copy. When all existing requests are completed then the old shadow copy is discarded.

But, having said all that, I don't know why you should have the problems you are experiencing, or, by extension, what to suggest to fix it.....