Hello; Can anyone help with this? I would like to change all of my apps to the updater, but I need to know if I should be moving to a different installation method or if someone is looking into the issue?
After getting wyBuild to work in my app and successfully running the initial blank update using the AutomaticUpdater.dll. (Please note that I did follow the instructions for disabling the DISABLEADVTSHORTCUTS=1.) I created a second update version to ensure the updates occur. My entire package is inside a single .msi. Thus the only difference between the version 1.1 and 1.2 is a different version of the same .msi file. i.e. 1.1\myapp.msi and 1.2\myapp.msi.Each version of the .msi contains the updated wyUpdate.exe and client.wyc files. After build I updated the "Files & Folders" tab with the appropriate .msi and then ran "Build updates". It created the two additional files. I then used the "Upload the Updates" and it pushed the files accordingly.I then ran the first version of my app and had it check for updates. It found the new update and showed the download progress, the ended with the notification that the updates would take place on the next start.I closed my app and restarted it. It turned on the wyUpdate.exe momentarily then seemed to rerun the .msi installer. This makes sense and I am OK with that, however, the app was not updated. I closed it and restarted it and it was still not updated with the new changes, but the updater check said it was.The 4 files files uploaded are the config file, the all to 1.1, the all to 1.2 and the 1.1 to 1.2. The 2 all's are full size and the 1.1 to 1.2 is very small, so I assume the compression and diff checks worked. Please help me understand what I might be doing wrong with this.
Hello; Can anyone help with this? I would like to change all of my apps to the updater, but I need to know if I should be moving to a different installation method or if someone is looking into the issue?
Hey Darrell,
To do "patching" you need to include your actual files, not the MSI files. Follow the walkthrough here: https://wyday.com/wybuild/help/walkthrough.php
You can choose to execute MSI files instead, but you lose a lot of the benefits of wyBuild in the process.
Does that make sense?
Tried to treat the update as separate files and not part of the .msi. This took some getting used to, but then I still run into the issue that the updates are not occurring. In the installer file directory setup, the "Application folder" is where my executable sits. I have sub folders below that that contain the dlls and support files. In the wyBuilder the "Your program's folder" ends up being the sub folder where the wyUpdater.exe is located. My apps stack, so how can I direct the updater to use the root "Application folder"? If I put the wyUpdater.exe in the root "Application folder", then will overwrite the ones built for the other applications. Using the "Program Files" folders does not seem to update anything. I added an additional test file to look for to try to find where they are updating to and the file is not on my system after an update when using these instead.
Hello; Got the updater to work, but I have a few question on this?1. I had to ensure that all files were in the same directory. I could not use sub-directories. Is this a known issue?2. I include the wyUpdater and client files in the installer package but not in the actual update. Do I need to update the new .msi? If this keeps working, I would never update the user .msi, I would just have them do an update, so why am I updating these files?3. Will the updater for 1 application actually be different than one for another?Asked this earlier and it matters as I don't want to fill up my customers computer with multiple copies of the same file.