Last post Mar 18, 2011 02:01 PM by geek.rutherford
Mar 14, 2011 10:16 PM|castlehills|LINK
Does IIS allow a new version of dll to be dropped in an already running website? Does it say the DLL is being used?
What will happen if we drop a new version of web.config? Is the outcome, a recycling of the application pool?
Mar 14, 2011 10:31 PM|tehremo|LINK
You can add a new DLL but the outcome may not be good. Is it the same version, just some updated code inside?
Adding a new web.config will trigger a recompilation of the site. So long as the config is good (no errors), you'll be fine.
Mar 14, 2011 10:36 PM|castlehills|LINK
I was not looking at the behavioral difference when a dll is dropped. I was looking at the impact to the users? I think IIS may not allow a new dll to be dropped to replace the same. Since the dll is being used by the worker process, probably it wont allow.
I dont know really.
The web.config is a config file. So, I dont think the site need to be compiled. No dll is made as part of this change.
Mar 15, 2011 03:42 AM|bala.sekhar|LINK
Yes your understanding is correct, you cannot replace a dll when application is running as it is used by workerprocess.
There is a filesystem watcher associated with the web.config file, upon doing any changes to it will invoke the recycling of corresponding application pool.
Mar 18, 2011 02:01 PM|geek.rutherford|LINK
From experience, yes you can drop a new dll into your web application even if the application is currently running in IIS and users are actively using it.
Nothing will prevent you from dropping in a new dll. In terms of behavior, the ASP worker process will recycle. It is the equivalent of making a change to the web.config file or deleting a directory within your we b app. This means your users will effectively
have their sessions killed.