Silent auto updateSolved

Used "wyUpdate.exe /skipinfo /fromservice" for a Windows Console Net Core app and it works.

Don't use /fromservice unless you're calling from a service. Why? Because when things fail no one will know why.

We try to design APIs and interfaces so they can't be mis-used, but man oh man is it hard. In the AutomaticUpdater we had a ForceCheckForUpdate() function that we said to use sparingly. Everyone used it all the time. Which is wrong and is the cause for all of the problems people have with the AutomaticUpdater.

We named /fromservice so specifically because we thought it would be a deterrent from using it with anything other than a service. And yet people (not just you, a ton of people) use it from anywhere. And then when things don't work right they get confused.

Long story short:

You want no UI? Create a service. Not a console app. Not a Windows app. A service. And follow the article.

Anything else? Follow the silently checking for updates article.

Both articles here: https://wyday.com/wybuild/help/

Having related issues here, having trouble getting wyUpdate commandline switches working as expected.

I have v1.0.4 of my application installed on my test machine, and v1.0.5 ready to go on my update server. Running wyUpdate.exe pops up the update dialog as expected.But wyUpdate /quickcheck /justcheck /outputinfo shows nothing (nothing written to stdout). /outputinfo without a filename doesn't seem to do anything, contrary to the documentation.With /outputinfo=wy.txt, wy.txt contains the version and release notes as expected.

And I have been completely unable to get wyUpdate to return the expected 2 with any combination of /quickcheck /justcheck /noerr - or rather, I suspect I must be reading it wrong.

(At this stage I'm just running it from cmd, and checking %errorlevel% for the result - though I'm doing this in the first place because I wasn't seeing the results I expected when running it from Process.Start() ).

What am I doing wrong?