Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Dynamic updates of program exe 1

Status
Not open for further replies.

Trowser

IS-IT--Management
Dec 16, 2002
125
GB
I want users to be able to update my program when a new version comes out but I have no idea how to do it.

IE they start up the program it goes to a server or intranet site checks the version number of the one on there and if the one on the server is a newer version it either initiates a download and overwrites itself, or it informs the user that there is a new version of the program.

I tried to do a search but it keeps timing out (since this has prolly been asked loads of times)
 

I presently do the same thing you are looking to do over my companies network. However I use the creation date versus version (much easier). The process that I use is ...

1. At startup check public server directory for newer exe
2. if found then shell companion program and end
3. companion program notifies user that it is updating
4. companion program then copies newer exe over existing
5. companion program then shells parent program and then ends

I hope this helps, Good Luck

 
Thanks for the info vb5

I understand what process to do now I just have to figure out how u do it :)

hint hint :)
 

Look up the shell function, the sleep function, play around with a timer (you want to allow parent to remove itself from memory before trying to copy over it or you will get an error), have a look at the filedatetime function, and remember to use unc paths as not every user will have the drive mapped as you may have. Also the companion program should not have any references that the parent program does not have, that way you do not need to have a seperate install. Also you will want to place a check in your parent program to look for the necessity of installing a new version because you have added references or new controls that were not distributed with the origional package. I use a text file (filedatetime again) that I create before I create the new package, so its creation time is greater/newer than the old exe but it will be older than the new exe.

I hope this helps, Good Luck

 
ok thats cool VB5 just what I need to start playing :) and get this bit sorted.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top