Some questions

Ah, the command line interface is documented here:

http://wyday.com/wybuild/help/commandline.php

Excellent! One down

Lastly since I'm rolling my own wyUpdater version, I have setup it to check at a specific path. I tried pushing a new version of wyUpdater, from the old wyBuild (2.6.10), and that didn't make my program want to update. Then I tried pushing a new update to my program and it also did not update wyUpdate. So am I correct in understanding that it will only update wyUpdater when I build something with wyBuild 2.6.11? And lastly if that is the case, what happens if I forget to update my version of wyUpdater and push out a new version of my program using a newer wyBuild?

1) The input field with http in wyBuild, could use a "when clicked" clear the help text

It does in Vista, Windows 7, and above. We can't do it in Windows 2000/XP (at least not without reimplementing the textbox, which will solve one problem and create 1000 others).

2) I there a way to make an update from the command line?

Yep, but I see you've already answered this yourself. Just use the wyBuild Commandline Builder.

3) I have hacked the wyUpdate.exe so that it instead of warning users to close the program that it is updated, that it simply kills the windows, just like as if one had pressed the kill window button. I'm using install-on-restart, so I don't really see the big harm. Maybe this could be added as a flag?

If we add this as a flag people might start using it, and I don't think this is a good idea. A better idea is to close all your apps before you call wyUpdate.exe to begin updating.

4) When starting up a program with command line arguments, after the program is updated, the program is started with the command line arguments.

If you're using the AutomaticUpdater use the "Arguments" property. If you're using wyUpdate as a standalone updater then simply execute the application after the update has completed.

Lastly since I'm rolling my own wyUpdater version...

See How to make a custom version of wyUpdate

1) The input field with http in wyBuild, could use a "when clicked" clear the help text

It does in Vista, Windows 7, and above. We can't do it in Windows 2000/XP (at least not without reimplementing the textbox, which will solve one problem and create 1000 others).

Aha, fair enough 🙂

4) When starting up a program with command line arguments, after the program is updated, the program is started without the command line arguments.

If you're using the AutomaticUpdater use the "Arguments" property. If you're using wyUpdate as a standalone updater then simply execute the application after the update has completed.

I'm using AutomaticUpdater. After looking at the documentation I'm just wondering why this is not the default? Instead of every application having to repass the arguments

I'm still a bit confused about wyUpdate.exe. I guess I'm a bit of control freak and want to know exactly what it is doing 😀

If I'm not rolling my own wyUpdate.exe, when exactly is wyUpdate.exe updated? When you release a new version of it, or when I release a new version of my software and there is a new version of wyUpdate available from you?

If I'm rolling my own wyUpdate, when exactly will it self-update? I checked the article you are referring to (http://wyday.com/wybuild/help/custom-wyupdate-version.php) and I didn't really say.

And is the version that wyBuild builds for me, signed?

If I'm not rolling my own wyUpdate.exe, when exactly is wyUpdate.exe updated? When you release a new version of it, or when I release a new version of my software and there is a new version of wyUpdate available from you?

We've updated the How to make a custom version of wyUpdate article with a "When wyUpdate self-updates" section.

And is the version that wyBuild builds for me, signed?

wyUpdate.exe is code-signed, but the wyUpdate self-updates aren't signed. We plan to add this in an upcoming version.