I have a ClickOnce app that is frequently launched from another application via a URL. The URL includes some command-line arguments that load data, etc.

Since the frequency of launching the app is so high, I want to cut out the check for version updates. So I implemented my own checking through the ApplicationDeployment class to avoid it. It works fine if you launch from the Start Menu once the app is installed.

However, we also want to preserve the launch via URL behavior because it is advantageous in so many ways. But when launching via URL, the update check is always performed -- it seems IE isn't smart enough to look for the app in the local download area to see if it is already installed or not...

Does anyone know of a way to get the "don't check for updates automatically" behavior while still using the URL launch mechanism?

Actually, it looks like the issue is a Catch-22 in the ClickOnce model. If you launch with a URL, IE will always touch base with the host and check the version, updating if necessary, regardless of whether or not the app is flagged as "Don't check version". However, if you launch from the Start Menu, ClickOnce disables command-line arguments.

Has anyone found any way around this, or know of a MS plan to fix it?