1: Don't try to look for updates for picture files since...when do those change, really?  Like, never.  If they do change, for that particular release, use option #2:

2: Have the updater compare versions and just download the exe file you have hosted automatically.  As an option, you could have that exe file only 'patch' instead of 'install', but the program's so small that's not a big deal.

Option #3, which I wouldn't prefer, is to disable the support for updating and remove it from the program since it's now a dead feature.

—

“I don’t know half of you as well as I should like; and I like less than half of you half as well as you deserve.”
— Bilbo Baggins, from his speech on his eleventy-first birthday.

Another option is to make the server have a list of updated files in each version. A list of which files changed since previous versions. Then send that list to client and client can compare list to what version the client have. Then the client download the missing files and update them in the installed directory.

Ex:

Version 2.3-2.2 GwFreaks.exe, Map.jpg
Version 2.2-2.1 GwFreaks.exe, Map.jpg, Skill_Gale.jpg

Then if the client has version 2.1 and latest is 2.3 the client download Skill_Gale.jpg from version 2.2 and the Map.jpg and GwFreaks.exe from version 2.3

Or is this not a good option?

I realize it's a lot of work, Zyo, but...what else are we working on?  I haven't seen much discussion about GWFreaks in the last couple of weeks.

I think the easiest one to implement first would be a 'do not check for update of these files' which you could then do for all the *.jpg or whatever extension you use for pictures for the map and for skills.  Since that's the way the system seems to work now (by checking each individual file and comparing it to the server), I think that would work best, simply saying 'don't check picture files'.

I think, of the three options, that's the one that involves the least amount of work.

—

“I don’t know half of you as well as I should like; and I like less than half of you half as well as you deserve.”
— Bilbo Baggins, from his speech on his eleventy-first birthday.

Another issue is that the update was working with an XML file that was returning missing files, XML means binary files in base64. With the map cut off the download is about ~12 meg since they can't be compressed as the Installer is. So updating is slower for nothing.

Another issue, is that the server got updated last with with the latest version of .NET framework and seems to removed the "Enter" in the patch note... that's why is only on a single line.

I've change job, and I'm doing stuff that will actually paid me. I sill need food and an apartment.

Wanna GWFreaks turn commercial with money involved? On a side note GWFreaks server takes 2 gig per day to run so don't think you can host it on your local internet connection.

The tool will be still be updated over time but probably not major update. When Chapter 2 will be out, the tool will be updated to make sure new classes are working well.

My conclusion is, considering the low number of update their gonna be, take it easy and download the file as you do for Winamp, ICQ, MSN, name it... the updater was a cool feature I got fun doing it, with over 1000 files it is just not working well.

Zyo
GWFreaks co-founder

GWFreaks client is coded in VB.NET using framework 1.1

GWFreaks server is coded in VB.NET too but framework 2.0

Source code will be unlikely released, but if want to create an updater from scratch... because the current one have nothing good at all, good luck.

- Sending 1 files at the time for update is not a valid solution.
- Sending file in a XML is probably not good either because of the binary encoding overhead.
- Having to create a list of each files modify for each release doesn't see to be interesting from my point of view. What if we add a new map that have 300 parts? Who gonna write the updater file?

The best approach would be (What I can think at the moment):

- The client send the date of his most recent file (for example 2005/04/04).
- Server compute what files had changed since the date.
- Return data using a custom blog of binary (zipped would be excellent for instance).
- Client find a way to shut down itself, download the file, replace himself and other files and restart.

This approach seems simple but you have to exclude file such as template and config since they may be modify everyday but the client.

The updater could be done in C++... GWFreaks call the updater, GWFreaks close, the update replace everything and relaunch it. The server could be a page in PHP, ASP, ASPX or almost anything.

If the update required 1 exe with 3 dll that take 400+ kb, not sure if it's good. The current updater is about 10kb + updater image.

I'm willing to help you if needed, I have no issue programming with C#, VB.NET and C++. I've works with all of them for years. My current job is in C#.

Hehe good luck and happy programming.


Zyo
GWFreaks co-founder