'New version available!'

[Michael Bulgrien]

If deletion of the executable is controlled via a command line parameter, then it could still be deleted when automated by the "install now" link... but would not be deleted if downloaded and executed later.

[GreenMoose]

Cirrus only checks for updates automatically when it starts.

No plans for checking during a session at e.g. once a day or so (or maybe even configurable like in other apps "check for updates every XXX")?
I tend to have my folder-compare session open constantly, with refreshing it now and then and then copy some files.
Since comparison of the files in this folder session is opened in new tab, it won't check for updates then either I guess.
(Guess same issue if not /solo switch is used having an opened session all the time?).

Thanks.

*Edit: This seems to work with Build 456, i.e. I had a session opened from 2nd of June and today 9th of June, after a refresh, I got the "New version available" link.

[Tom]

Would you guys consider also (maybe optionally) prompting the user each time to (re)run the program? The main consideration here is to give me a second to reenable security software after the update process. (It will then prompt to update the file signature/hash of the executable that wants to run.)

[GreenMoose]

Would you guys consider also (maybe optionally) prompting the user each time to (re)run the program? The main consideration here is to give me a second to reenable security software after the update process. (It will then prompt to update the file signature/hash of the executable that wants to run.)

Isn't that already enforced by the installer?
I can't continue install if BC3 is already running.
---------------------------
Setup
---------------------------
Setup has detected that Beyond Compare 3 is currently running. Please close all instances of it now, then click OK to continue, or Cancel to exit.
---------------------------
OK Cancel
---------------------------

[Tom]

Isn't that already enforced by the installer?
I can't continue install if BC3 is already running.

You'll see from my message that you quoted it says "after the update process".

[Michael Bulgrien]

I think Tom means something like this:



Those that do not want an auto restart would have to clear the check mark.

[Tom]

Thanks, Michael -- but I was thinking more of a post-install prompt. Your example is still prior to the process of running the MSI installer or whatever ends up being used. Here's the way a different program does it...

[Michael Bulgrien]

I was thinking more of a post-install prompt. Your example is still prior to the process of running the MSI installer or whatever ends up being used. Here's the way a different program does it...

Thanks Tom.

Your example is from an interactive installation of an MSI package. When updating BC3 from the "New version available..." link, a quiet (non-interactive) installation is performed. Therefore, the option to launch the app must be passed as a runtime parameter (hence the need to specify the option prior to installation).

If you want the full interactive GUI during the BC3 installation, download the installation package and run it manually instead of having the automated update process do it. You will then have the post-installation option you are looking for:

[Michael Bulgrien]

The checkbox in my sample dialog could just as well have been:

[ ] Perform interactive installation

If you check it, then BC3 does an interactive install instead of a silent one...and you get the post-installation prompt at the end. Would that work for you (if the Scooter team implements it)?

[Tom]

The checkbox in my sample dialog could just as well have been:

[ ] Perform interactive installation

Absolutely. That's exactly what I'm asking for if it's doable and low-impact on the development process. However, the term interactive might be confusing to some since that could also imply that you'd be selecting whether or not to install the shell extension and so on.

The "full" installation is probably best done as a separate action, whereas the final prompt seems to maintain the concept of updating the existing install. (Still, if "full" is more likely to be implemented than "final prompt only" I'd be amenable to that.)

[Aaron]

Thanks for the interesting ideas going back and forth. I've appened some of the notes into our tracker entry on the Updater.

[Michael Bulgrien]

I don't think "Full" any clearer than "Interactive". Of course, it could just be reversed:

[x] Perform silent installation

And have the user uncheck it to get the user agreement, upgrade screen, and final prompt to restart.

[Tom]

I don't think "Full" any clearer than "Interactive".

Possibly not -- I know about the concept of interactive installs vs. silent from corporate deployments and the like, but I think non-techies would be hard pressed to see where setting the upgrade dialog for desired behavior doesn't qualify as "interactive". Maybe there's a less jargon-laden way to describe it, that's all I'm saying. Either way it works for me.

Thanks for the interesting ideas going back and forth. I've appened some of the notes into our tracker entry on the Updater.

Thanks much, Aaron!