Run ClickOnce at the URL, but do not check for updates

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?

+3
source share
2 answers

Nothing needs to be fixed for Microsoft. This is the alleged behavior of the ClickOnce online deployment. It checks to make sure it is online and checks to make sure that it launches the latest version, and then it starts. If you do not want this to be done, you need to configure it to run online and offline.

I think that if you install it offline and still call it via http-url, it will still check for updates, but I would not swear at that. If this is an online application, you can call it via a shortcut in the Start menu.

.NET 3.5 SP-1 .NET 4.0, , /. , , .

+1

URL? , : -.

0

Source: https://habr.com/ru/post/1704217/


All Articles