Ah, I seem to have resolved this issue. Once I unchecked 'Create a catch-all update for corrupt installations', everything changed dramatically. Now all my updates are around ~100kb. Awesome.
Hi,
I've been noticing that my update patches are huge regardless of how small the changes might be and I'm curious why they're so large. Let me explain my build process so you understand where wybuild comes into play.I have a build server that compiles (using teamcity), all the projects ( a mix of .net, vb6, asp.net and classic asp) into a folder. Installshield then picks up these files and creates the setup (a normal windows installer decompressed setup). That's when I grab the files that installshield has combined, and use them when creating the update.
Now, I'm sure all the files have new date created attributes since all previous files will be deleted. But essentially they should be the exactly the same as before as long as the code didn't change. Does wybuild do a binary check between the files to detect changes or does it just check for simple attributes like date created/modified etc?
My setup when decompressed is around 150Mb, the updates from 'all to latest' is around 40mb, and from 'previous to latest' (with only a basic change in text, not code) is still around 20mb. I've tried removing the client.wyc from the updates but still no change occurs, the updates remain large. Could there any explanation of why the updates are so large?
ThanksJohn
Ah, I seem to have resolved this issue. Once I unchecked 'Create a catch-all update for corrupt installations', everything changed dramatically. Now all my updates are around ~100kb. Awesome.