MichaelHi,
I'm trying to use our custom wyUpdate. I followed all steps exactly as described in http://wyday.com/wybuild/help/custom-wyupdate-version.php. But when I click "Build wyUpdate" in wyBuild project for main application, default version of wyUpdate.exe is copied to the output folder instead of our custom version. Is it by design or did I miss something? I checked generated client.wyc and I can see correct wyUpdate self-update URL pointing to our server. Am I supposed to copy our custom wyUpdate.exe to the output folder manually?
Clicking "Build wyUpdate" copies the latest verison of wyUpdate (our compiled & signed version) and it generates the latest version of the client.wyc file.
If you want to make a customer version of wyUpdate you actually have to get the wyUpdate source code and compile it in a compiler.
MichaelOf course we built our own version from wyUpdate source code. And it's signed now with our key instead of wyDay's. That's not what I asked. You have a help page that describes how to make a custom version of wyUpdate. I did everything as described. For our main application, in "File -> Properties" on the "wyUpdate" tab, self-update server file points to .wys file on our server. But when I click "Build wyUpdate" it still copies the standard version of wyUpdate signed with wyDay's key instead of pulling custom version from our server. How is it supposed to work? How can I make sure that I configured everything correctly?
But when I click "Build wyUpdate" it still copies the standard version of wyUpdate signed with wyDay's key instead of pulling custom version from our server.
Clicking Build wyupdate always copies *our* version of wyUpdate.exe. That's by design. Obviously you have to use your version of wyUpdate.exe in your app.
Does that make sense?
MichaelYes, thanks, we will replace it with our custom version and include custom version with the application setup. What is the best way to check if wyUpdate self-update is configured correctly for our custom version? I don't want our custom version to be replaced with your version of wyUpdate when you publish a new wyUpdate version.
One way to test if you configured everything correctly is to release a new version of wyUpdate (just change the version number is AssemblyInfo.cs and in your custom wyUpdate wyBuild project file). Build the updates, upload them to your server, then release a new version of your app.
If wyUpdate updates to your new version (along with your app updating) then everything is configured correctly.
MichaelThank you, will do that. Last question: will self-updates work if I rename wyUpdate.exe to Update.exe?
Yep.
What problem?
