My head is starting to hurt this afternoon so I'd love any tips anyone can
offer. :-)
I'm currently going with the concept of putting all my DLLs in the bin/
directory inside my web application's root directory. This is working fine.
However, when I want to upgrade one of the DLLs (all of which are
strong-named and have unique version numbers that change each build), I have
to perform two steps:
1. Copy the new DLL into the bin/ directory, overwriting the existing DLL
2. Update the web.config file to implement the bindingRedirect option for
the new DLL version
Between the first and the second steps taking place, my application fails
(because it can't find the version of the upgraded DLL that it is expecting
things to bind to). This may only take a couple of seconds, but with the
thousands of hits we are getting on our web site this will most likely cause
at least one or two users to receive an error message.
Is there an obvious solution to this that I'm missing?
--
(O)enone