I am unsure which method to use. Here is my scenario:
1. I have a main install which is complex and is about 150MB including suppport files, databases and related installers. I distribute this on disk but it can be downloaded.
2. I set up an update project based on version number and that works fine but the update (via the web) is slow because of the 150MB download.
3. My new versions usually only involve a few dll's and the help manual, totalling only 3MB or so. It involves a version number change to trigger things internally (like running upgrade scripts etc).
4. If I create a new install for the upgrade over the same folder from the main install/update with just the 4 files that have changed, the update deletes all other files in that folder and I can't seem to make them leave them alone. I have folder sync off.
So what is the best way to distribut the new version where only the 4 files or so are affected? Is this a patch? I am a little confused by this process but willing to try it if that is what I should be doing. Or, can I make the upgrade leave all other files alone?
Thanks for any advice.
Geoff Schaller
FOLLOW US
Get the latest news in Application Packaging