We're planning on making this better for non-.NET languages. Namely, we plan to make wyUpdate cache updates / server files when wyUpdate operates in "standalone mode".
Better integration with unmanaged C++?
Would love to have a way to better integrate your software than calling an external process and waiting for its return value.
One of the worst aspects of this interface is that if the user chooses "yes, update", the external process has to connect to the server again and establish that an update is available (and if so, which one). Which it just finished doing on the previous run, in order to report a return code back to our software to say "yes, there is an update".
So, clunky for the end-user (not terrible, just less than optimal).
That could be cool. Might be necessary to use a shared ticket number, so you don't get stale data from a previous pass.
Might be nicer to have a .dll or .lib to link to with an API I can call directly!