It looks like this has been asked for before but I'm just throwing my hat into the ring too. I'm deploying wyBuild & wyUpdate in a qt application and will be using the "silent update" method of calling wyUpdate.exe. A very nice flag would be wyUpdate.exe /quickcheck /patchnotes (spit it to STDOUT) or wyUpdate.exe /quickcheck /notesToFile=foo.txt
With this functionality I could present the user with a dialog box containing the latest version number and all the features instead of simply "new version is available - update now?" .
So far I'm really impressed with wyBuild & wyUpdate, you guys have done a fantastic job!
A very nice flag would be wyUpdate.exe /quickcheck /patchnotes (spit it to STDOUT) or wyUpdate.exe /quickcheck /notesToFile=foo.txt
OK, we'll add it to the 2.7.0 release (or if we make a 2.6.16 release we'll add it to that).
So far I'm really impressed with wyBuild & wyUpdate, you guys have done a fantastic job!
Thanks, that means a lot.
Thanks a ton for the follow up. By the way: I went from installing wyBuild to having a functional updater integrated in my application under two hours...pretty sweet. Next up - LimeLM integration 🙂
We now output more info on STDOUT or a file (your choice). See: http://wyday.com/wybuild/help/wyupdate-commandline.php#outputinfo.
You guys rock...I'll be implementing this tomorrow 🙂
Is this in 2.6.16.4 ? I updated wyBuild this morning, tossed up a new patch on my server and the using the following command isn't yielding any output:
C:\PhotoMonkee>wyUpdate.exe /quickcheck /justcheck /noerr /outputinfo
Running just wyUpdate.exe /quickcheck does pop up with a dialog indicating the list of changes, however.
Just a followup, running it with the file option /outputinfo="test.txt" does dump the info to a file.
Is this in 2.6.16.4 ? I updated wyBuild this morning, tossed up a new patch on my server and the using the following command isn't yielding any output:
C:\PhotoMonkee>wyUpdate.exe /quickcheck /justcheck /noerr /outputinfo
Yes, this is in 2.6.16.x and above. wyUpdate will write to STDOUT, but in the example you posted the STDOUT won't be written to the console window (due to the nature of how Windows starts GUI apps from the console window).
So, when you read the STDOUT programmatically within your code everything will work fine.
...and correct you are 🙂 Silly me thinking the console would actually pipe STDOUT to...you know...the output 🙂
Thanks again for the help. Enjoy the rest of the weekend and this quickly melting snow (yay!).
Thanks again for the help
No problem.
Enjoy the rest of the weekend and this quickly melting snow (yay!).
Hopefully no more snow this year.
