Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<h1>Automatic Updates</h1> <p><a href="http://msdn.microsoft.com/en-us/library/s22azw1e.aspx" rel="noreferrer">Choosing a ClickOnce Update Strategy</a> (<strong>Making Updates Required</strong>)</p> <p>One options is to set up automatic updates to your software and mark them as required by setting the minimum required version in your deployment manifest. You can set this in the properties dialog in Visual Studio, or through configuration with the following tag: <code>&lt;deployment install="true" minimumRequiredVersion="1.0.0.0"&gt;</code>. The minimum required version checks the version of your assembly, and if it is not at least what you specify here it will force an update.</p> <h1>Programmatic Updates</h1> <p><a href="http://msdn.microsoft.com/en-us/library/cc558901.aspx" rel="noreferrer">How to: Add On-Demand Programmatic Update</a></p> <p>Another option that will allow you more control of when and how often the update occurs is to do the updates programmatically. You can use the ClickOnce API to check for any updates on the deployment server and install them once your application has been run. You can have far more control over what updates should be installed, how they are installed, and how you notify the user of the updates. If your application is generally a long running instance, you could also set up timers to run in the background every so often to do the updates as well.</p> <p>Here is an example implementation that polls on an interval: <a href="http://msdn.microsoft.com/en-us/library/cc558902.aspx" rel="noreferrer">Example</a>.</p> <p>You can also combine the above two update methods.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload