How to: Deploy an Updated Version of an Application

Retired Content
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. To create client business applications using current Microsoft technologies, see patterns & practices' Prism.

If you have set the update settings as described in How to: Set the Basic ClickOnce Publishing Properties for a ClickOnce publication, the application will always try to check the deployment server for updates before it starts. If there are no updates or if the deployment server is unreachable, the application will start the last installed version. If the deployment server has an update available, the user will be prompted that an update is available and they can accept the update or skip it. If they accept the update, the updated files will be downloaded before the application starts, and the new version will start instead. There are many variations of this behavior possible because of the different update settings in ClickOnce.

In this procedure, you will launch the client application, and the application will determine that an update is available and then run that update.

Because the update you will be applying adds the Credit Card Module to the application, you will also have to update the Profile Catalog Services Web service to make sure that the module information for the Credit Card Module is active so that it will be loaded when the application checks the Profile Catalog Services Web service to see what modules should be loaded.

For more information about this procedure, see Deploying an Updated Version of an Application.