Updating VB.NET Program (exe)

[Sarah]

Hello, I would I go about letting my Windows VB.NET program connect to a
webserver and update itself if there is a new version of the exe? Sample
code would really be appreciated!

Thanks.

[Ken Tucker [MVP]]

Hi,

http://msdn.microsoft.com/msdnmag/is...S/default.aspx

Ken
-------------
"Sarah" <sa********@powertechcanada.com> wrote in message
news:WGuud.17245$U47.7021@clgrps12...
Hello, I would I go about letting my Windows VB.NET program connect to a
webserver and update itself if there is a new version of the exe? Sample
code would really be appreciated!

Thanks.

[Rob Willaar]

Hi Sara,

I have made an app downloading a zip using the Internet in a seperate
folder.
Then i add a key to runonce in the registry and tell the user to restart to
update the app.
This will start a simple app just backup the app, check the zip and
unzipping the downloaded files.

BITS is nice but also more complicated to implement.

"Sarah" <sa********@powertechcanada.com> schreef in bericht
news:WGuud.17245$U47.7021@clgrps12...

Hello, I would I go about letting my Windows VB.NET program connect to a
webserver and update itself if there is a new version of the exe? Sample
code would really be appreciated!

Thanks.

[Blitz Krieg]

Is there ANY other trigger possible? RunOnce is not a very nice way to
do this. One way, that I have been thinking about... is to have my
application check for an update everytime it runs, and if it finds one,
the spawns a small updater engine, and terminates the original
application, when the updater engine is done replacing files or
whatever, it calls the 'new' application, and the update engine shuts
down. All the user sees is the main application stopping and
restarting with no human interaction. As long as you are familar with
the Process Class in .NET? It is not two hard.

Main App Runs (Checks for Pending Update?)
Main App Spawns Update Engine
Main App Shutdown

Update Engine (Download Files, Replace, Etc.)
Update Engine Spawns Main App (Updated, Etc.)
Update Engine Shutdown

Main App Continues...

8)

[Chris Calzaretta]

This is the nice part of .net you nolong need to quit the application to
write over the .dll files

So what I am saying is that you can be running your application. If you see
an update grab the new dlls and
create your object again.
your done

"Blitz Krieg" <Sc*******@DSLExtreme.COM> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

Is there ANY other trigger possible? RunOnce is not a very nice way to
do this. One way, that I have been thinking about... is to have my
application check for an update everytime it runs, and if it finds one,
the spawns a small updater engine, and terminates the original
application, when the updater engine is done replacing files or
whatever, it calls the 'new' application, and the update engine shuts
down. All the user sees is the main application stopping and
restarting with no human interaction. As long as you are familar with
the Process Class in .NET? It is not two hard.

Main App Runs (Checks for Pending Update?)
Main App Spawns Update Engine
Main App Shutdown

Update Engine (Download Files, Replace, Etc.)
Update Engine Spawns Main App (Updated, Etc.)
Update Engine Shutdown

Main App Continues...

8)