title: Is manually (and silently) updating a ClickOnce app going to be a stable way of deploying updates?
body: <p>I've deployed an application inside a corporate network and I want the update process to require less attention from users, similar to how Google Chrome install updates - in the background. I don't need to give the user a choice to update.</p>
  
  <p>I've used the <code>System.Deployment</code> library to detect when new ClickOnce updates are available and install them automatically. I'm wondering if its necessary to restart the app after the update is complete. Currently I invoke <code>Application.Restart()</code> at the end of my update script.</p>
  
  <p>But what if (to make the update process more transparent for the user) I performed a 'silent' async update and then displayed an icon prompting the user to restart the app to apply the changes? Would this make the app unstable in any way?</p>
  
  <p>Furthermore, if I ran my custom <code>InstallUpdate()</code> process on a timer, say every 30 minutes, would ClickOnce be stable to continue to update for every new version that was released even thought the user has not restarted (nb: I'm expecting the updates to only apply once the user restarts the app)?</p>