Re: self-autoupdate vb exe
- From: "Michael C" <mculley@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 27 May 2005 16:43:18 +1000
"Hunter" <huntertaylor@xxxxxxxxx> wrote in message
news:3fnqjdF8i4g9U1@xxxxxxxxxxxxxxxxx
> how might this be implemented?
>
> user runs an exe which immediately when started should check a network
> server location
> to determine if a newer version exists?
>
> if it does, copy the new exe, terminate current exe and start the new copy
>
> running the exe from the network location is not allowed, it must reside
> on local
> desktop
I've done this in 2 different apps and think I found a fairly good way to do
it. Your app should check is it needs updating and if it does it should
download a seperate exe, maybe called update.exe and then exit itself. Then
update.exe will copy the new version of your ap, run it and exit. The great
thing about doing it this way is that you can supply an updated update.exe
with each new release, so if requirements change you can change it. If all
your update code is stuck inside your app you are stuck with code you might
have written 2 years ago.
Don't forgot to put in some retrys when copying the files to make sure your
app has had time to exit.
Michael
.
- References:
- self-autoupdate vb exe
- From: Hunter
- self-autoupdate vb exe
- Prev by Date: Trapping Keypress in a VB6 MDI form
- Next by Date: Re: System-wide hooking, VB+ASM
- Previous by thread: Re: self-autoupdate vb exe
- Next by thread: Re: self-autoupdate vb exe
- Index(es):
Relevant Pages
|
Loading
