Respect user decision on if updated .exe should be run

[ErrorDodo]

Current we just blindly auto run the installed .exe after an update.
This can cause errors when we are using the setting;

AutoUpdater.ClearAppDirectory = true;

AutoUpdater.NET/ZipExtractor/FormMain.cs

Line 296 in f3f1bf2

var processStartInfo = new ProcessStartInfo(executablePath);

[ravibpatel]

You can provide the executable path you want to execute in XML in case if it was changed as shown below.

<executable>bin\AutoUpdaterTest.exe</executable>

[ErrorDodo]

When setting ClearAppDirectory to true. It removes all the files correctly but then ZipExtractor errors out saying it cannot run the .exe

There is currently no way of telling the ZipExtractor to not run a file after update to stop this from happening

We sunset one project for a new one with different ways on handling updates and it got us in an infinite updating loop.

[ravibpatel]

Providing the new executable path relative to the old one if it was changed should fix this, cause ZipExtractor extracts the new updated zip before executing the executable. Is there a reason you don't want to re-execute the application after a new update? Even after providing a new executable path in the XML it is going in update loop, then it can mean assembly version of the new executable is still the same. Does that be the case?

[ErrorDodo]

Okay that makes sense, thanks for clarifying it