Please add these features

I really like wyUpdate, but I would like to see some features in wyBuild:

- Please offer an option to edit the name, icon and the other brands of the wyUpdate.exe- Please add more options to the "Update Actions" -Page. It would be nice to run commands/programs before or after the update routine. It would also be nice to be able to "kill" a process (not a service).

I've never seen a tool which creates an update mechanism/deployment that easy. Please continue work on these nice tool.

Please offer an option to edit the name, icon and the other brands of the wyUpdate.exe

You can replace all image branding in wyUpdate by editing the theme within wyBuild. You can also change the titlebar by going in wyBuild to File -> Properties -> wyUpdate and typing your new title.

As far as other branding goes you'll have to rebuild wyUpdate from the source code if you want to replace the "wyUpdate" string you see in the UAC dialog. The reason you need to rebuild from source code is because the UAC reads this string from an embedded resource in the executable (only if the executable is code signed).

Does that make sense?

Please add more options to the "Update Actions" -Page. It would be nice to run commands/programs before or after the update routine.

You can already execute files before and after updates. See Executing files in your update.

It would also be nice to be able to "kill" a process (not a service).

wyUpdate already checks that no programs are running in your app's directory when the update is happening.

I'm wondering that I didn't saw the options in the properties dialog. Thanks for your reply! I will take a look into it.

My problem is, that I dont have the ability to remove the wyUpdate-text from the updater .. or change the application icon. Or the name of the built executable. In some cases it should be possible, or its necessary to hide (3rd party) components in your software project.

You can modify the source code to replace the icon and wyUpdate name (see: How to make a custom version of wyUpdate). We can't automate this step because it would require us to replace resources in the executable (and thus resign wyUpdate.exe with a code signing certificate).

But you can modify the source code freely.

ok, I understand the limitations cause of the signing process. But another thing is, that http://wyday.com/wybuild/help/executing-files.php is not working accurate. I defined a file to be executed after the update, but it's only executed if the update was a 'full update', not incremental (patch).

But another thing is, that http://wyday.com/wybuild/help/executing-files.php is not working accurate. I defined a file to be executed after the update, but it's only executed if the update was a 'full update', not incremental (patch).

When you select a file to be executed it is only executed when your app updates to that version. Let's say you have 2 versions: 1.0 and 1.1. 1.0 is the original version of your app and 1.1 is your first update. In 1.1 you specify a file to be executed. When your user updates to 1.1 the file is executed.

Now let's say you create a new version, 1.2. In 1.2 you must specify the file to be executed again -- the 1.1 version isn't executed. The reason this happens is that patches are "direct patches" (1.0 -> 1.2, 1.1 -> 1.2) and not "incremental patches" (1.0 -> 1.1, 1.1-> 1.2). In wyBuild 2.7 we're adding incremental patches.

Does that make sense?

I used the word incremental to describe the small kind of update. But yes, I specified to execute that file in every version I created, but its only executed when the updater does a full update.

I mean, when I changed a file in a directory where a 1.0 client is located, wyUpdate decides to use the "all"-version of the update-file - and executes the binary file is specified, after update. If I just change nothing, wyUpdate uses the small update file - and does not execute the binary after the update.

So you are creating new updates with no changes, but with the exe marked as 'to be executed'?

http://www.wedigo-hosting.de/0212171058_1.pnghttp://www.wedigo-hosting.de/0212171103_2.png

If wyUpdate uses "npm.all.to.1.0.1", the npm.exe is executed.But if the "npm.1.0.0.to.1.0.1" is used, it won't be executed and I don't understand why.

I was able to reproduce the problem. It only happens if the file set to be executed after the update has not changed in the update. Either that, or if the whole folder has not changed. (I tested with only a single file).

Are the files E:\Wedigo.net\1.0.0\npm.exe and E:\Wedigo.net\1.0.1\npm.exe identical?Also, are the folders E:\Wedigo.net\1.0.0 and E:\Wedigo.net\1.0.1 identical?

I'm guessing that's a bug in WYUpdate...Here's a workaround for now.Include a new bat file in your project, and execute npm.exe through that bat file.

Then for each of the versions 1.0.0 and 1.0.1, modify the bat file - even if the npm.exe files are identical, as long as the bat files are different (just add a few spaces or modify something in them), wyUpdate seems to execute them.

Oops, this is a pretty big bug. Thanks for spotting it. The fix will be squeezed into 2.6.15. Omaer's right about the work around.

Thanks for your replys. The specified file was identic, but the folder wasn't. I was fairly sure that it is a bug.

While the update was executed, I noticed that the messages were not translated (I use a modified langfile). But my system language is also not english.

wyBuild 2.6.16 is now out -- this bug is fixed.