It looks like this might be the culprit:https://wyday.com/forum/t/1058/execute-after-updating/#post-5363
Has there been a fix to this issue yet?
I decided to try to execute wyUpdater via Process.Start instead of using the AutomaticUpdater since I need it to check for updates every single time and not launch the app if it hasn't updated yet. In order to do this, I check for updates, and if I find some, I launch the updater and close the app (logic below)
private static bool CheckForUpdates() { // Check for updates Console.WriteLine("Checking for updates ..."); Process updateProcess; try { updateProcess = Process.Start("wyUpdate.exe", "/quickcheck /justcheck /noerr"); } catch(Win32Exception) { Console.WriteLine("Could not find update application -- running current version."); return false; }
if (updateProcess == null) { return false; }
updateProcess.WaitForExit();
bool updatesAvailable = updateProcess.ExitCode == 2; if(updatesAvailable) { Console.WriteLine("Updating ...");
// Update Process.Start("wyUpdate.exe", "/skipinfo");
return true; }
return false; }
Additionally, I mark my .exe in my files to execute after updating is finished. I build wyUpdate and updates and then upload to the server. The client recognizes the update and installs it, but never relaunches my application when complete. Is there something I am doing wrong, or do you have another methodology for achieving this behavior?
It looks like this might be the culprit:https://wyday.com/forum/t/1058/execute-after-updating/#post-5363
Has there been a fix to this issue yet?
Yes, but we haven't released wyBuild 2.6.15 yet. We're going to push it out on Monday even if it means making an additional 2.6.16 release a week later to finish features we had planned for 2.6.15.
In the meantime you can use a batch file in the "Temporary folder". That is, create a simple batch file whose singular purpose is to execute your app. Just pass in the "%basedir%" variable as a commandline argument.
Sorry for the trouble.
Thanks for the info! Can't wait for the new version!
Good afternoon,
Is there any info on when this update will be released? We have decided to purchase licenses, but we will need this bug fixed before we go live.
Thanks,Justin
Hey Justin,
We had delayed the release to fix and re-test after one of our beta testers found a show-stopper bug. We plan to release 2.6.15 early Monday morning. Sorry for the delay.
We're very near completion. We've found one last bug that were concerned about. We're fairly certain it wasn't in previous releases, so we'll probably have to bite the bullet and just fix it.
2.6.16 is now out. This bug is now fixed.