title: How to deploy a DLL that is constantly changing?
body: <p>I have created several small applications that use my own DLL. The problem is, this DLL is constantly changing. My current solution to this problem is that I have a Setup project in the class library solution that creates and registers the DLL. In all my applications I then have to open the solution and re-reference the newly created/registered DLL. <strong>Then</strong> I have to re-compile their setup projects, uninstall the old applications, and then re-install the new application. </p>
  
  <p>There has to be a better way and I'm just not sure because I'm fairly new to all this. I have looked into ClickOnce but I don't think that will solve my issue as I cannot publish a class library. I have looked into checking version numbers but I must be doing something wrong because it doesn't work either.</p>
  
  <p><em>I understand that once a DLL is created and being used in an application it should essentially not be touched. I do not have that option in this situation. It is constantly updated. Done.</em> </p>
  
  <p>So, is there a better way? A point in the direction of a guide or related question/answer/forum would be greatly appreciated.</p>
  
  <p><strong>Edit</strong>: The DLL is not constantly changing during runtime but it is constantly evolving to allow more functionality and detail within the other applications. Also, one big thing I guess I should have mentioned is the Public interface is constantly chaning - usually adding new methods.</p>