Lauch Application After Update

I noticed by default the update process does not launch the mai application when it's done updating. Makes sense, after all how would it know what to run....I also noticed that neither does wyBuild after it updates itself. Myself and my users find this a little annoying.

So I started to play around with "Execute file after updating has finished". However I can not get this to work at all. AFTER updating has FINISHED. Yet it winds up launching my selected EXE before the update then I get a message that the process needs to be shutdown prior to updating. Once I kill the process, updating continues then my app launches again??? In some cases (completely random) I wind up with my application running twice.

I'd be very grateful for any insight on how to set this up properly.

I should also note, unchecking that checkbox and running it again, it works fine. No process issues and I'm simply left with the desktop to launch the application myself after the update completes.

Before I can help you I need to know more about your setup.

  1. What version of wyBuild are you running? The current version is 2.6.17.1.
  2. What version of wyUpdate are you running? The current version is 2.6.16.4.
  3. Are you using the AutomaticUpdater, or are you using wyUpdate as a standalone updater?

If you're using wyUpdate as a standalone updater, the way to launch your app after an update has completed successfully is to click a file in wyBuild, click the "Execute file after updating is complete." and uncheck the "Wait for execution to finish before continuing checkbox".

Thanks for the reply!

1. The program self updated two days ago. So I assume the current version. Sorry, I'm not in front of it right now.

2. Same 2.6.14...sound familier.

3. AutomaticUpdater. VB.NET

Launch appApp downloads updateExit appLaunch app - app process runs, then closes then the update progresses then the process runs again while it's updating and the update program complains about the process needing to be closed. After the update finishes, the app process run again and all is well.

On a side note, I don't even have to click CLOSE PROCESS. It just brute forces it's way past it.

I have execute file selected and I have wait unselected. I have also tried both selected with the same exact outcome.

There's a bug in the current and previous versions of the AutomaticUpdater (v 2.6.16.4 and older) where under certain circumstances when wyUpdate was being self-updated and the update process was being started when your app is restarted (instead of when clicking the "Install now" option on the AutomaticUpdater), then your app won't start after the update.

We'll be fixing this bug.

In the meantime make sure you always include the latest wyUpdate.exe with your initial installers.

Does that make sense?

What you said makes sense in itself but my app "is" restarting. Only it's restarting before the update is finished and causing the wyupdate to complain about the process needing to be closed. But then it does it anyway and my app launches.

Are you running multiple instances of your app? Are you making any special actions before or after starting the installation process?

Are you executing files withing your wyBuild project file? (If so, don't -- uncheck the "Execute file" checkbox, rebuild your updates, upload them, and try again).

Hold on. Lets back up. Are you saying that by DEFAULT with no extra settings my application is "supposed" to relaunch on it's own?

This is my first time using your app and when my application did NOT relaunch on it's own I simply thought that's how your app worked. Especially since your own wyBuild updated itself a few days ago and it also did not launch after the update. So I looked for a way to get it to launch after the update thinking that was my responsibility to include that functionality.

Hold on. Lets back up. Are you saying that by DEFAULT with no extra settings my application is "supposed" to relaunch on it's own?

The default for the AutomaticUpdater is to restart your app after a successful update (or even after an error happened).

The default behavior for wyUpdate in "standalone" mode is to not launch anything. Just do the update and get out of the way.

Which are you using? wyUpdate in standalone mode or the AutomaticUpdater. You shouldn't use both. That is, you should have a shortcut to wyUpdate.exe for your users to run if you're using the AutomaticUpdater. Also, you shouldn't directly run wyUpdate.exe from your app if you're using the AutomaticUpdater (let the AU handle starting and stopping wyUpdate).

Especially since your own wyBuild updated itself a few days ago and it also did not launch after the update.

Again, like I said above, there's a bug that the app using the AutomaticUpdater won't restart after the update if the following conditions are met:

  1. wyUpdate is being self-updated. (That is, an old version of wyUpdate is being replaced with the newest version).
  2. The AutomaticUpdater is being used.
  3. The user doesn't click the "Install Now" menu option on the AutomaticUpdater, but instead lets the updater run on the next start of the application.

We're going to fix this bug. In the meantime you can avoid this problem by doing one or both of the following:

  1. Including the latest wyUpdate.exe in your installer for your app. This means clicking the "Build wyUpdate" button and including the latest wyUpdate.exe file and client.wyc file in your installer.
  2. Manually clicking the "Install Now" option on the AutomaticUpdater when an update is ready to install. OR Programmatically calling the InstallNow() function if the update is read to install and the user is closing your app.

Does this make sense?

The default for the AutomaticUpdater is to restart your app after a successful update (or even after an error happened).

Ok, we're on the same page now. This is just a bad coincidence. I first started using your app while it has this bug. With the lack of documentation (this being it http://wyday.com/wybuild/help/) not stating otherwise I had no choice but to assume that was how your app worked.

Which are you using?

As I stated earlier "3. AutomaticUpdater. VB.NET"

You shouldn't use both.

I'm not.

Also, you shouldn't directly run wyUpdate.exe from your app if you're using the AutomaticUpdater

I'm not.

We're going to fix this bug. In the meantime you can avoid this problem by doing one or both of the following:

1. I'm already doing that.

2. Going the install now route works.

You might want to find a way to let new users know or mention somewhere (http://wyday.com/wybuild/help/automatic-updates/) that with AutomaticUpdater their app should re-launch on it's own.

I guess I'll wait for an update. Thanks.

Reply
Discard post