This page contains additional options which control the way your ClickOnce application will behave.

You can also use this page to enter up to 8 file associations. File associations are used to associate file types with your application on the end users system.

Installation Options

Allow URL parameters to be passed to application

Check to ensure your application will be passed the URL query string parameters when it is launched from a URL.

You can access the URL parameters through ApplicationDeployment.ActivationUri in your application code.

Make application available to users offline and online

Check to allow your ClickOnce application to run when the user cannot access the deployment URL or UNC path. Checking this also enables you to set various other options for your offline application (see below).

Checking this box sets the InstallToMachine flag to true in the ClickOnce manifest. Although Microsoft documentation states that if this is false then the application will not be installed, it does not appear to be true. In fact the application is ALWAYS installed to the users machine. Setting this flag to true does however enable a host of additional options (see below).

Allow application to be installed from multiple URLs

Check this box if you want the same application to be able to be deployed and updated from multiple URLs (e.g. an intranet site and an external web site). Checking it causes the deploymentProvider tag to be omitted from the deployment manifest (.application) file. Ordinarily you should leave this box unchecked.

Manifest Options

Retain registration-free COM details from existing manifest file

Check this box if you are using registration-free COM in your .Net application and your entry point executables manifest file contains COM type references. In that case, ClickOnceMore will attempt to transfer the type references contained within your manifest file into the ClickOnce manifest file it creates. See Registration Free COM for more information on registration-free COM and ClickOnceMore.

Use the Application Name as the .manifest file identity

Check this box if you want the Application Name (see General for more details) to be used as the assembly identity name in the .manifest file. If this is not checked, the main .exe file name (see Application Files for more details) will be used. The standard setting for this is unchecked. Only check this box if you wish to create several distinct ClickOnce packages using the same executable file and you need to differentiate between them.

Remove ".application" from assembly identity name in the deployment manifest

Check this box if you have upgraded from V2.4 of ClickOnceMore. V2.4 incorrectly dropped the .application extension from the assembly identity. By checking this box you can force that behaviour with later versions for ClickOnceMore for better continuity in your existing deployments.

Offline Application Options

Start Menu Folder

This field supports macro replacement. See Macros for more details.

Enter a name for an additional Start Menu level which will appear between Publisher and Application Name.

Applications installed via ClickOnce and able to run offline always have a Start Menu entry. The default path for the entry is: Start -> All Programs -> Publisher -> App Name. Entering this field adds an extra level resulting in this path: Start -> All Programs -> Publisher -> Extra Level -> App Name.

Create desktop shortcut

Check to create a desktop shortcut for your application. The shortcut will be named after the application.

Block application from being activated via a URL

When this check box is cleared (the default), the application runs automatically after installation. Checking this box specifies that the end user can start the application only from the Start Menu, blocking the application from being started by using a URL.

File Associations

Add up to 8 file associations for your installed application.

You must set the trust level to full trust and target .Net 3.5 in order to use file associations. See Trust Levels to configure trust levels. See Requirements to set up a dependency on .Net 3.5.

Once your application has been installed it can then be launched by double clicking files of the associated types. When it is launched in this manner you can determine the file it was launched with by checking the ActivationData of the current app domain. AppDomain.CurrentDomain.SetupInformation.ActivationArguments.ActivationData[0]


The file extension that you want your application to be associated with. DO NOT put a dot at the front.

You should try to ensure that this file extension is not already in use. If at install time the file association is already being used, the new file association will not be registered with the system.


A short description of the file type.

This will appear in the hover tooltip and in the Type column in Windows Explorer for files of this type.


Enter the full path of an icon file (.ico) to be displayed in Windows for files of this type. ClickOnceMore will automatically deploy this file with your application.

Prog Id

Used to register your file type with Windows.