I have a ClickOnce application that often launches from another application via a URL. The url contains some command line arguments that load data, etc.
Since the launch frequency of the application is so high, I want to disable checking for version updates. Therefore, I performed my own validation through the ApplicationDeployment class to avoid this. It works fine if you start from the start menu after installing the application.
However, we also want to keep the launch at the URL, because it is beneficial in many ways. But when starting at the URL, the update check is always performed - it seems that IE is not smart enough to look for the application in the local download area to find out if it is installed or not ...
Does anyone know how to get the automatic "don't check for updates" behavior when using the URL launcher?
Actually, the problem seems to be with Catch-22 in the ClickOnce model. If you run the URL, IE will always touch the base with the host and check the version, update if necessary, regardless of whether the application is marked as "Do not check version." However, if you start from the Start menu, ClickOnce disables the command line arguments.
Has anyone found any way around this or find out the MS plan to fix this?
source
share