wyUpdate niggling issues

For number 2 I should note I'm using C# and Process.Start to kick off the wyUpdate (after it returns a code of 2), and I'm using the /skipinfo flag. This is the same whether it's staging which restarts the app, or production which doesn't.

Regarding issue #1: you need to configure the project in the user account that you want to build th eupdates. So, log into the user account and run wyBuild. You'll see the theme you want doesn't exist because it's created under your user-account folder.

Regarding issue #2: I need more information about exactly what your problem is. Do you get errors? If so, what are they? Try launching wyUpdate manually: does it behave differently? Why?

Hi,

Thanks for the reply, issue #1 is now resolved!

Here is some more info about issue #2.

I have an application that must update itself. It uses C# and Process.Start wyupdate.exe with /quickcheck /justcheck /noerr to check if there is an update. When it receives return code 2, it will do another Process.Start with /skipinfo and the wyupdate project is set to auto close on finish. The application then kills itself so that wyupdate can update it, on the assumption wyupdate will start it again when it finishes.

I have two wyp files because they use different upload locations for staging vs production updates, and I find that with the staging wyp, wyupdate relaunches the application once it has finished, but with the production wyp it does not. The production project file is literally a copy of the staging project with only those locations changed.

wyupdate doesn't display any errors and there is nothing in the event viewer or anything. I've also tried putting a bootstrapper app around this and can see that wyupdate is returning 0 after the update so no errors there.

The application also appears to be up to date when I relaunch it manually, so it seems everything has gone well except wyupdate didn't relaunch it automatically after update.

If I launch wyUpdate.exe directly, it shows the update info, updates and then closes automatically and does not launch the application afterwards.

Hi,

Any progress on this? What is the expected behaviour?

I have had to do a partial workaround using the aforementioned bootstrapper app to launch the update and then have that wait to see if the app starts after the update, and launch it if it doesn't start (because I see both behaviours depending on the build).

This is not ideal and I still have the same problem if I need to update the bootstrapper but that should be a lot less common.

>> "The application then kills itself so that wyupdate can update it, on the assumption wyupdate will start it again when it finishes."

If you execute your app after the update, and uncheck "Wait for execution to finish", *and* the update completes successfully, then yes, that assumption is true. See: https://wyday.com/wybuild/help/executing-files.php

Note: you have to do this for every single update in wyBuild.

If the update does finish successfully, then no, your app won't be restated.

So, how do you start your app on failure? If you're using the AutomaticUpdater, it handles it. If you're not using the AutomaticUpdater, then you have to handle it: https://wyday.com/wybuild/help/wyupdate-commandline.php#startonerr

>> "wyupdate doesn't display any errors and there is nothing in the event viewer or anything. I've also tried putting a bootstrapper app around this and can see that wyupdate is returning 0 after the update so no errors there."

You can always output errors if you're running from services: https://wyday.com/wybuild/help/wyupdate-commandline.php#outputinfo

https://wyday.com/wybuild/help/wyupdate-commandline.php#logfile