At program startup check if same process is already running: using System.Diagnostics; static void Main(string[] args) { String thisprocessname = Process.GetCurrentProcess().ProcessName; if (Process.GetProcesses().Count(p => p.ProcessName == thisprocessname) > 1) return; }
It’s a security feature that allows your users to verify that any updates really originated from the publisher of the version you installed before. This is a basic property of Public Key encryption. On top of that you can have your certificate authorized by a trusted peer so that the details of the publisher supplied … Read more
So I had this same problem with WSUS and it turned out that IIS 8.5 was not binding to my ipv4 ip address, but was binding to ipv6 address. when I accessed it via localhost:8580 it would translate it to the ipv6 localhost address, and thus would work. Accessing it via ip was a no … Read more
You can figure out the registry keys to be added, using Windows Sysinternals Process Monitor (Previously known as RegMon). Capture Events when you install your app using ClickOnce with default file associations. It will record all the registry operations (lots of them). You would need to use some filters to easily identify the registry keys.
You can try using this command to clear the ClickOnce cache: rundll32 dfshim CleanOnlineAppCache
Other responses here are not correct or helpful. It is incorrect to state that it never needs removing. One such example I experienced recently was when the application had a need for administrative privileges. Any attempt to embed administrative requirements into the manifest will result in the application not even compiling while ClickOnce is still … Read more
As the error message says, there are two options. First, you as a developer should modify the version number of the ClickOnce manifest. This is done at the ClickOnce tab of the project settings. Note that ClickOnce version has nothing in common with your assembly (assemblies) version. Another option is to uninstall the application and … Read more
AFAIK you can’t really use ClickOnce end-to-end to deploy a service; there are issues with both the file locations (ClickOnce installs into a user’s profile) and installation (ClickOnce is largely side-effect free). You can, however, write a service as an exe that can self-install/uninstall from the services list, like so; basically, you write it as … Read more
You can revert back to an older version on the server side by changing the server manifest file. When the client restarts the application, it will see that it has a different version than what the server says is the ‘current’ version, and it will download the new one. This server manifest file usually always … Read more
The problem for me was that the checkbox “Signing the ClickOnce manifest” was checked. If you are not using signing uncheck it in Project Properties->signing->sign the clickonce manifests