PDA

View Full Version : wsupdate.exe



NewsArchive
03-28-2007, 10:53 AM
Maybe I am overlooking it, or not looking in the right place, but I don't
find much about running and interfacing with the Web Update Client.

What are the different online commands I can use with it, and, mostly, how
do my application knows if there is an update, or not?

Well, in fact, maybe the question should be: Does my application NEED TO
KNOW if there is an update, and if yes, how does she knows... ???

Thanks,
Bernard

NewsArchive
03-28-2007, 10:53 AM
Bernard,

If you pass the /C command line switch, wupdate.exe only checks if an update
is available. If it returns 1, an update is available. If it returns 0, no
update is available. All return values < 0 are error codes.

But your application does NOT need to know if there is an update available.
I would suggest to start the wupdate.exe client from your application or add
a "Check for Update" Shortcut.

You can add a "Check for Update" menu item to your application, add a "Check
for Update" button, check for updates at application startup (and use
interval checking), etc., etc. You can do whatever you want.

Then, if an update is available, just check in your Web Installer Package if
your app is still running ("Detect Active Application" in a Loop). If this
is the case, ask the user to terminate the application. You can also gently
close the app or kill an app, but both actions are not recommended.

Or, use the /C switch to check if an update is available. If yes, close
your application and automatically start the web update process. This makes
sure the app is not active.

Does this help?

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

NewsArchive
03-29-2007, 02:00 AM
Hi Friedrich/Bernard,

>is available. If it returns 1, an update is available. If it returns 0, no
>update is available. All return values < 0 are error codes.

I use this with very good results in a web update install that I have
with my client. I have it set up to check at startup. I checked this
out with my LAN cable disconnected and it responded immediately,
obviously finding that there was no connection to the server. I don't
know how it would behave on a dialup, but since all the installs for
this client are on broadband connection it's not an issue for me.
Knowing that it returns within milliseconds when the network is down
was good enough for me to just let the program check every time it
starts:)

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

NewsArchive
03-29-2007, 10:18 AM
Arnor,

> Knowing that it returns within milliseconds when the network is down
> was good enough for me to just let the program check every time it
> starts:)

Good trick, thanks!

Bernard

NewsArchive
03-29-2007, 10:19 AM
Arnór,

Wow, very cool :)

Friedrich

NewsArchive
03-29-2007, 10:19 AM
Friedrich,

> But your application does NOT need to know if there is an update available.
> I would suggest to start the wupdate.exe client from your application or add
> a "Check for Update" Shortcut.

Yes, I thought about this after my post. It's not required for the
application to know if there is an update or not, as long as the update
knows.... ;-)

> Or, use the /C switch to check if an update is available. If yes, close
> your application and automatically start the web update process. This makes
> sure the app is not active.

I may go for something like that, as I want everything to be silent, unless
there is some problem.

Thanks, Friedrich, and yes, it does help!

Bernard