ClickOnce Deployment for Windows Forms Applications

Describes the purpose of ClickOnce, and how it solves key problems in deploying Windows Forms applications to client computers.

Describes the different ways in which you can deploy a ClickOnce application to client computers, including the benefits and limitations of each strategy.

Describes the different options available for updating a ClickOnce application once it is installed, including automated update subscriptions and on-demand updates.

Describes some of the technical details behind how ClickOnce updates an application without downloading the entire file set.

Describes the security implications of deploying Windows Forms applications over the network, and how to instrument your deployment to request elevated permissions from the client computer.

Explains how Authenticode is used in ClickOnce application deployment.

Explains how to deploy key ClickOnce dependencies such as the .NET Framework to client computers.

Demonstrates how to write code that checks for an application update in response to a user request or some other event.

Explains how to change the Web site or directory that ClickOnce uses to check for updates to your application.

Explains how to prevent users from launching installed applications via the deployment's URL.

Describes the most common problems encountered when deploying ClickOnce applications, and how to resolve them.

Describes a technology for securely elevating a ClickOnce application's permission level on the client computer.

Explains how to use .NET Framework utilities to deploy your ClickOnce application.

Demonstrated how to manually alter an application manifest to include individual support URLs for each prerequisite.

Demonstrates the steps for the one-time configuration required to deploy a ClickOnce application to a client using trusted application deployment.

Describes how ClickOnce works with the new architecture for persisting application and user-configuration state.

Explains how to download application assemblies only when they are first used by the application.

Demonstrates how to retrieve parameters passed in the URL used to run a ClickOnce application.

Describes the various ways you can store and access data on the client computer and fetch data from remote sources.

Explains how to mark a file in a ClickOnce deployment as a data file so that it is stored in the data directory on the client computer.

Describes the cache used to store ClickOnce applications on the local client computer.

Describes the properties, methods and events available to developers who wish to implement custom upgrade behavior into their ClickOnce applications.