Publishing ClickOnce Applications
For the latest documentation on Visual Studio 2017, see Visual Studio 2017 Documentation.
When publishing a ClickOnce application for the first time, publish properties can be set using the Publish Wizard. Only a few of the properties are available in the wizard; all other properties are set to their default values.
Subsequent changes to publish properties are made on the Publish page in the Project Designer.
You can use the Publish Wizard to set the basic settings for publishing your application. This includes the following publishing properties:
Publishing Folder Location - where Visual Studio will copy the files (local computer, network file share, FTP server, or Web site)
Installation Folder Location - where end users will install from (network file share, FTP server, Web site, CD/DVD)
Online or Offline availability - if end users can access the application with or without a network connection
Update frequency - how often the application checks for new updates.
For more information, see How to: Publish a ClickOnce Application using the Publish Wizard.
The Publish page of the Project Designer is used to configure properties for ClickOnce deployment. The following table lists topics
|How to: Specify Where Visual Studio Copies the Files||Describes how to set where Visual Studio puts the application files and manifests.|
|How to: Specify the Location Where End Users Will Install From||Describes how to set the location where users go to download and install the application.|
|How to: Specify the ClickOnce Offline or Online Install Mode||Describes how to set whether the application will be available offline or online.|
|How to: Set the ClickOnce Publish Version||Describes how to set the ClickOnce Publish Version property, which determines whether or not the application that you are publishing will be treated as an update.|
|How to: Automatically Increment the ClickOnce Publish Version||Describes how to automatically increment the Revision number of the PublishVersion each time you publish the application.|
For more information, see Publish Page, Project Designer
This dialog box allows you to specify how the files in your project are categorized for publishing, dynamic downloading, and updating. It contains a grid that lists the project files that are not excluded by default, or that have a download group.
To exclude files, mark files as data files or prerequisites, and create groups of files for conditional installation in the Visual Studio UI, see How to: Specify Which Files Are Published by ClickOnce. You can also mark data files by using the Mage.exe. For more information, see How to: Include a Data File in a ClickOnce Application.
This dialog box specifies which prerequisite components are installed, as well as how they are installed. For more information, see How to: Install Prerequisites with a ClickOnce Application and Prerequisites Dialog Box.
This dialog box specifies how the application installation should check for updates. For more information, see How to: Manage Updates for a ClickOnce Application.
The Publish Options dialog box specifies an application's deployment options.
|How to: Change the Publish Language for a ClickOnce Application||Describes how to specify a language and culture to match the localized version.|
|How to: Specify a Start Menu Name for a ClickOnce Application||Describes how to change the display name for a ClickOnce application.|
|How to: Specify a Link for Technical Support||Describes how to set the Support URL property, which identifies a Web page or file share where users can go to get information about the application.|
|How to: Specify a Support URL for Individual Prerequisites in a ClickOnce Deployment||Demonstrated how to manually alter an application manifest to include individual support URLs for each prerequisite.|
|How to: Specify a Publish Page for a ClickOnce Application||Describes how to generate and publish a default Web page (publish.htm) along with the application|
|How to: Customize the ClickOnce Default Web Page||Describes how to customize the Web page that is automatically generated and published along with the application.|
|How to: Enable AutoStart for CD Installations||Describes how to enable AutoStart so that the ClickOnce application is automatically launched when the media is inserted.|
|How to: Create File Associations For a ClickOnce Application||Describes how to add file name extension support to a ClickOnce application.|
|How to: Retrieve Query String Information in an Online ClickOnce Application||Demonstrates how to retrieve parameters passed in the URL used to run a ClickOnce application.|
|How to: Disable URL Activation of ClickOnce Applications by Using the Designer||Describes how to force users to start the application from the Start menu by using the designer.|
|How to: Disable URL Activation of ClickOnce Applications||Describes how to force users to start the application from the Start menu.|
|Walkthrough: Downloading Assemblies on Demand with the ClickOnce Deployment API Using the Designer||Explains how to download application assemblies only when they are first used by the application using the designer.|
|Walkthrough: Downloading Assemblies on Demand with the ClickOnce Deployment API||Explains how to download application assemblies only when they are first used by the application.|
|Walkthrough: Downloading Satellite Assemblies on Demand with the ClickOnce Deployment API||Describes how to mark your satellite assemblies as optional, and download only the assembly a client machine needs for its current culture settings.|
|Walkthrough: Manually Deploying a ClickOnce Application||Explains how to use .NET Framework utilities to deploy your ClickOnce application.|
|Walkthrough: Manually Deploying a ClickOnce Application that Does Not Require Re-Signing and that Preserves Branding Information||Explains how to use .NET Framework utilities to deploy your ClickOnce application without re-signing the manifests.|
|NIB: How to: Optimize an Application for a Specific CPU Type||Explains how to publish for a 64-bit processor by changing the Target CPU or Platform target property in your project.|
|Walkthrough: Enabling a ClickOnce Application to Run on Multiple .NET Framework Versions||Explains how to enable a ClickOnce application to install and run on multiple versions of the NET Framework.|
|Walkthrough: Creating a Custom Installer for a ClickOnce Application||Explains how to create a custom installer to install a ClickOnce application.|
|How to: Publish a WPF Application with Visual Styles Enabled||Provides step-by-step instructions to resolve an error that appears when you attempt to publish a WPF application that has visual styles enabled.|