title: Is switching a dll file enough to update a published ASP.NET application?
body: <p>I've got an ASP.NET application on the server which I can't compile again currently (until some repairs are done). In the meantime though it would be good if I could update a .dll it uses.
  So the application bin folder on the published server looks like this (names are abbreviations):</p>
  
  <pre><code>myapplication.dll
  funcdll1.dll
  funcdll2.dll
  </code></pre>
  
  <p>Now a collegue of mine said it should work that I switch out the funcdll1.dll vs. a new version of the same dll (same functions that the myapplciaiton.dll uses, but the underlay for these functions (an external dll that is integrated into that one) is completely new. </p>
  
  <p>So I tried switched the dll out, stopped the application pool and started it again, but seemingly no change to the executed program (it still behaves in the old way). "The old way" is that a database command does not work as the password for the database has changed (which is corrected in the new .dll).</p>
  
  <p>Now I'm wondering if it is possible to do this this way? Or if I did something wrong?</p>
  
  <p>Edit:
  As it was asked: The applicaiton itself is a webservice, where non asp.net programs connect to and execute the functions and get the results back (all via https naturally).<br>
  The password is directly in the .dll without any web.config file (additionally there were some mandatory optimizations in the .dll from what I know).</p>