Publishing ClickOnce Applications
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 and Publish Wizard.
The Publish page of the Project Designer is used to configure properties for ClickOnce deployment. The following table lists topics
Describes how to set where Visual Studio puts the application files and manifests.
Describes how to set the location where users go to download and install the application.
Describes how to set whether the application will be available offline or online.
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.
Describes how to automatically increment the Revision number of the Publish Version each time you publish the application.
For more information, see Publish Page, Project Designer
Application Files Dialog Box
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. For more information, see Application Files Dialog Box.
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.
Prerequisites Dialog Box
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.
Application Updates 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 and Application Updates Dialog Box.
Publish Options Dialog Box
The Publish Options dialog box specifies an application's deployment options.
Describes how to specify a language and culture to match the localized version.
Describes how to change the display name for a ClickOnce application.
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.
Demonstrated how to manually alter an application manifest to include individual support URLs for each prerequisite.
Describes how to generate and publish a default Web page (publish.htm) along with the application
Describes how to customize the Web page that is automatically generated and published along with the application.
Describes how to enable AutoStart so that the ClickOnce application is automatically launched when the media is inserted.
For more information, see Publish Options Dialog Box.
How to: Publish Multiple Projects in a Solution
Describes how to automate the process using a macro to publish all the projects in a solution
Describes how to add file name extension support to a ClickOnce application.
Demonstrates how to retrieve parameters passed in the URL used to run a ClickOnce application.
Describes how to force users to start the application from the Start menu by using the designer.
Describes how to force users to start the application from the Start menu.
Explains how to download application assemblies only when they are first used by the application using the designer.
Explains how to download application assemblies only when they are first used by the application.
Describes how to mark your satellite assemblies as optional, and download only the assembly a client machine needs for its current culture settings by using the designer.
Describes how to mark your satellite assemblies as optional, and download only the assembly a client machine needs for its current culture settings.
Explains how to use .NET Framework utilities to deploy your ClickOnce application.
Explains how to use .NET Framework utilities to deploy your ClickOnce application without re-signing the manifests.
Explains how to publish for a 64-bit processor by changing the Target CPU or Platform target property in your project.
Explains how to enable a ClickOnce application to install and run on multiple versions of the NET Framework.
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.