Installing Omaha and applications via ClickOnce

When building release version of Omaha, the scons-out\opt-win\clickonce_deployment directory will contain all files required for ClickOnce.

All these files - bin\GoogleUpdateSetup.exe, bin\clickonce_bootstrap.exe, clickonce_bootstrap.exe.manifest and GoogleInstaller_*.application - should be placed on the same path on the server (there should not be any additional bin path for first two files)

The file scons-out\opt-win\clickonce_deployment\bin\GoogleUpdateSetup.exe is just a copy of scons-out\opt-win\staging\GoogleUpdateSetup.exe

When user's browser supports ClickOnce, requesting

http://your.domain.com/path/to/clickonce/GoogleInstaller_en.application?url-encoded-omaha-tag

URL will initiate Omaha to install application defined by tag. Note that the Omaha tag (similar to the one using for tagged metainstaller) must be URL-encoded.

For instance, here is how Google's ClickOnce URL for installion Chrome looks:

https://dl.google.com/update2/1.3.25.11/GoogleInstaller_en.application?appguid%3D%7B8A69D345-D564-463C-AFF1-A69D9E530F96%7D%26iid%3D%7B9406DAEA-01EF-4199-4A83-A2ED8B93D520%7D%26lang%3Den%26browser%3D4%26usagestats%3D0%26appname%3DGoogle%2520Chrome%26needsadmin%3Dprefers

There are several GoogleInstaller_*.application files in build output directory. They all do the same, the only difference between them is the localization of the ClickOnce part (not Omaha itself). You don't have to place all those files on your server, but only the files with the languages you need.