How do I build a "tiny update"?

I have read that these types of files cannot change between update versions, but this does not make sense to me. A patch or "tiny update" should be able to process these files and update them.

I'm not sure where you read that, but wyBuild can handle *all* files (exes, pdfs, dlls, word documents, images, etc., etc., etc.). It doesn't care what's inside the files.

This problems is almost always caused by the version in wyBuild that represents your old version doesn't match the version you're including with your installer and that's being delivered to your users.

Make sure the old pdf in your V! folder matches the pdf file on the customer's computer. Make sure the customer didn't modify the PDF, and make sure no other program modified the PDF on the target computer.

A good place to start is the step-by-step walkthrough.

Am I doing something wrong or am I missing the fact that wyBuild only works for exe, dll and the like and not support files (which for me change frequently without changing the exe)?

wyBuild supports all files. I'm not sure where you read otherwise.

Tell me if this helps.

I misread the comment in another post regarding the files that wybuild can process. My mistake.

The problem I think I am having is actually dealing with the location of the pdf file, not necessarily the pdf file itself. My install process creates a directory then copies the pdf file into it so once the application is installed it puts it into the "new" directory and is not where wybuild thinks it should be (I think), since the build points to where it is on my computer, not necessarily where it actually gets installed.

I think this will also happen with my data files, since they will be placed under the application data folder.

I have changed my wybuild project to point at what I thought was the proper directory. It said it did the update without errors this time, but the file did not actually update.

I am attempting to put this file into "C:\documents and settings\all users\application data\my data directory". In wybuild it gives you the option for current users app data folder - roaming and local. What is the difference? I put it under local but my guess is that is wrong. Also, we do install this under windows 7 - will wybuild point to the correct user directory automatically?

I ended up putting the directories under the common appdata folder and it worked!

The one thing I noticed is that I had turned off all updates within wybuild so I can force it to check for updates instead of it doing it automatically. It worked fine on my XP machine but the updates seemed to process automatically on windows 7. Is that normal?

You mean inside the Options (Tools -> Options) window in wyBuild? Do you have it set to "Never check for updates" on your Windows 7 machine?

I am using a windows 7 machine as a test install, so wybuild is not installed on it - I am installing my application with wybuild already built into it.

I just tried to open my installed application again on windows 7 and it did not auto update. Strange.

However, I do have another question (not related so I can ask in a new question if necessary). I put in my wybuild to use address "myserver.com" from my hosts file which it seemed to work ok. However, in my test environment the IP address of the server is not a fixed address, so after rebooting it now has a different address. When I went to check the update it failed when looking for the IP address from the one that was in place during the build. Does wybuild translate the name to the ip address? It seems that way, which now means I need to rebuild my update. That is what I was trying to avoid by putting the name in the hosts file so I would not have to worry about the IP address during updates (since there will be several people testing I thought this would be a good solution).

wyUpdate/wyBuild don't modify your download sites at all. They use what you give them.

I have found that when I build my client files yesterday using my hosts file name "myserver.com" all was well. Today I had to reboot my server which changed my IP address (this is a test environment). So I updated my hosts file to reflect the new address. When I tried to run the update, it said it could not connect to address 192.168.1.10 which was yesterday's address. So obviously it pulls in that IP address when it builds the client file and "hard-codes" the address instead of using "myserver.com". Once I rebuilt the client files and install files, uninstalled the reinstalled the new version, it then could find the updates.

Unless I am missing a setting somewhere, it obviously did not use the name from the hosts file; it used the IP address.