When a new version of the application is defined, a previous version that still runs acceptably can be defined as acceptable to run. For example, an acceptable-to-run version might contain a cosmetic bug that the most recent version fixes.
When the end user starts the application, the end user's WebClient instance downloads the latest application configuration file and checks if any updates are needed. At that point, WebClient might discover that the end user's version is defined (in the application configuration file) as acceptable to run. When this occurs, the end user is offered the option of downloading the newer version. If the end user so requests, WebClient downloads and applies the updates. For more information on acceptable-to-run versions, see
Deploying an Application
