Good Day,
In the past I got great tips and guidance for a problem I had using this forum. So I thought I would as the Guru's again for some more guidance/tips
What would be considered a good way to create a auto updater? Currently I have this in mind and semi working:
Client application updates:
For the database updates it seems it is going to be a bit more "interesting" and I do not have a working solution yet.
I had the following suggestions from various sites (my database uses MySQL/MariaDB for those who want to know)
For the database updates a "nice to have" would be that the update mechanism uses encryption/zipped with a password to prevent data theft.
Any suggestions/Ideas/Pointers? I would really appreciate it!
In the past I got great tips and guidance for a problem I had using this forum. So I thought I would as the Guru's again for some more guidance/tips
What would be considered a good way to create a auto updater? Currently I have this in mind and semi working:
Client application updates:
- Is checked from inside the app for a version number increment via http
- If the version number is higher then launches a downloader app
- the downloader app make a backup of the current app executable renames it to app.exe.backupdate
- the downloader app downloads the new installer (NSIS Created) and does a silent install
- launches the new update application when done
For the database updates it seems it is going to be a bit more "interesting" and I do not have a working solution yet.
I had the following suggestions from various sites (my database uses MySQL/MariaDB for those who want to know)
- Do a CRC check on the database, tables , columns, rows etc to see if the data is different
- Import small sql updates that overwrites or adds new data
- Use a xml file with the updates and apply the updates via code
- to a manual dif on 2 sql databases to create a new sql with the "updates"
- import a fresh database every time (not an option really database is 400+ megs and growing)
- export every records a small sql file number against indexes
For the database updates a "nice to have" would be that the update mechanism uses encryption/zipped with a password to prevent data theft.
Any suggestions/Ideas/Pointers? I would really appreciate it!