Can't get Patch to work correctly
Posted: Fri Feb 06, 2009 4:20 pm
I have been working on trying to properly apply a patch for over a week now. I must be doing something wrong because even after the patch installs on a client machine, the changes that were made do not appear on the client. Please bear with me on the details of this email because I wanted to lay out exactly what steps I have taken because I have ready your help and through some forum posts but am still unable to get the process to work correctly. In my sample below are the exact steps I took.
I have a current Compressed Web-Based EXE build. The version of the application as well as the setting in Project Properties is 6.0.0.0. I build the application and move all he web blocks along with myapplication_Setup.exe, myapplication_setup.7zip, and updates.ini to the web server. I download the application on the client computer and install the software. Everything is fine. For testing purposes of the update process, I want to make a small change, such as add a help.txt file to the installation directory. I go to the Files section under "Setup Archive" and add the file to the $TARGETDIR$. I then go to the "Update Packs section and add a new entry pointing it to my webserver path\\patches\\myapplication_Setup.exe. I create a new entry in the Versions menu for 6.0.0.0 and check off the Update Pack that was just created. I then go to Patches and create a new patch pointing it to the web install originally created. I click build patch and then copy the myapplication_setup.exe and updates.ini file from the patch directory to the web server under the patches directory. On the client computer, I run the upgrade process and it finds the upgrade. I tell it to install and it completes successfully. The problem is that after it install there isn't any help.txt file in the installation directory. I have tried this with many different scenarious such as making just a small change in the software and going through the same steps but after the update, the changes haven't been made. I can't get the update to update any of the files or add new files or anything. I must be missing something, but can't figure out what I'm doing wrong. Please help, because this software is getting ready to go to our external beta team and I want the install to be correct beforehand.
I have a current Compressed Web-Based EXE build. The version of the application as well as the setting in Project Properties is 6.0.0.0. I build the application and move all he web blocks along with myapplication_Setup.exe, myapplication_setup.7zip, and updates.ini to the web server. I download the application on the client computer and install the software. Everything is fine. For testing purposes of the update process, I want to make a small change, such as add a help.txt file to the installation directory. I go to the Files section under "Setup Archive" and add the file to the $TARGETDIR$. I then go to the "Update Packs section and add a new entry pointing it to my webserver path\\patches\\myapplication_Setup.exe. I create a new entry in the Versions menu for 6.0.0.0 and check off the Update Pack that was just created. I then go to Patches and create a new patch pointing it to the web install originally created. I click build patch and then copy the myapplication_setup.exe and updates.ini file from the patch directory to the web server under the patches directory. On the client computer, I run the upgrade process and it finds the upgrade. I tell it to install and it completes successfully. The problem is that after it install there isn't any help.txt file in the installation directory. I have tried this with many different scenarious such as making just a small change in the software and going through the same steps but after the update, the changes haven't been made. I can't get the update to update any of the files or add new files or anything. I must be missing something, but can't figure out what I'm doing wrong. Please help, because this software is getting ready to go to our external beta team and I want the install to be correct beforehand.