Our webserver is IIS 6.0 which runs on Windows 2003 server.
We have several DotNET applications (around 50 DLLs) running under a single virtual directory.
All of them are under a single application pool.
I am updating a DLL file.
After update, if I try to access a function from the updated DLL, I am getting unanticipated errors.
If I recycle the application pool and tries to access the function then it works fine.
1. What are the causes for this scenario? How to overcome this?
2. Currently, I have scheduled the App. Pool to automatically recyle the worker
process 4 times a day in a 3 hour interval. Is that right?
3. How to manage the application pools and woker processes settings optimally?
4. When I update the DLL file, how can I enforce that the updated DLL files are
synchronized with the application pool? (ie. without manually recycling the app. pool)
Thanks in Advance