title: Setting up DLLs so we can update production ASP.NET app w/o full publish or app restart
body: <p>We have DLLs that contain hundreds of custom client processes that are kicked off from an ASP.NET application.  Our clients run these processes while performing data entry, and typically there's only 1 process per client.  On any given day, we might update 2 or 3 of these processes.  </p>
  
  <p>Currently these are all housed in a series of DLLs, which means that we are publishing our application a couple times per day.  As a result, any logged-in clients get booted out of the system since the publish causes an app restart.</p>
  
  <p>Is there a way that we can update these DLLs without requiring a full publish each time?  </p>