customy wyUpdate location

And while I'm on the topic of custom locations, I have the following scenario.

The app launcher "app.exe" in "app" folder for historical reasons launches "app\bin\mainApp.exe". I added AutomaticUpdate control to mainApp.exe and set wyUpdateLocation to "..\wyUpdate.exe" (placed it in root "app" folder according to the docs). If I launch "wyUpdate.exe" by hand, everything works fine.

Inside the app the update control spins, but gives the following error: "wyUpdate ended before the current update step could be completed." It does launch wyUpdate.exe in the root folder, but nothing good happens...

Is it possible to place wyUpdate.exe and client.wyc in some custom folder ("app\update" for example)? From the docs it seems that no, this isn't supported. Why not?

It is supported (and has been since the first beta of wyUpdate), but we don't advertise the feature because it's really meant for users who know what they're doing. Simply use the "basedir" commandline argument with the full path to the new base directory. For example:

wyUpdate.exe -basedir:"C:\Program Files\Your App"

In the AutomaticUpdater you'd use the wyUpdateCommandline property. Make sure you put quotes around the path, or else things will fail pretty quickly when wyUpdate tries to access the folder "C:\Program".

Inside the app the update control spins, but gives the following error: "wyUpdate ended before the current update step could be completed." It does launch wyUpdate.exe in the root folder, but nothing good happens...

This general "premature exit" error is pretty crummy -- we're fixing it for the next version of wyUpdate coming out on Monday (barring no further delays). But if I were to guess, I'd say wyUpdate isn't being found. I'll check into this problem and get back to you.

Thanks!

Well, I'd say wyUpdate is being found. At least it's being launched. I'd guess it can't find client.wyc (since the current dir is probably "app\bin".

This was a bug in the AutomaticUpdater. It didn't properly expand your relative path, and thus it couldn't connect to wyUpdate to begin talking to it. We've just fixed this and it will be included in the release coming Monday.

wyBuild 2.6.12 is out. This bug is now fixed.