Hi, We are new to wyBuild and are trying out the product. I've read the guide and watched the video, as well as looked through the forums, but I'm still a bit confused so hoping you can help me with some (probably) newbie questions on using wyBuild and wyUpdate. I apologize for such a long post ahead of time.
So we have an app that is made up of many files (about 3.5Gb worth) and we have a 'launcher' for the app that does various things which includes a 'Check for Update' button. We also update with patches every few weeks (for now). So my question is about how best to set this all up. I have a 'dev' folder on my desktop which holds the files (including the launcher files). Assuming I'm building for a fresh user install (I use Actual Installer to build the setup.exe file including all the version 1.0 files), I understand that I would use wyBuild to build the 'blank' initial install. But do I build that including all the files in the initial (version 1.0) build? (I assume so).
Ok, so this is a rather large (wyUpdate) file that get uploaded to our server. After I have wyUpdate.exe and the client.wys file generated, do I add them to my dev folder with all the other files, then package all that up in my installer file for the first time? (Because our launcher has the button that calls wyUpdate.exe to check for updates, so wyUpdate.exe has to be in the app directory.)
Then say we have a new 'version' of the app with a few new or changed files. In wyBuild, I create a new 'version 1.1' folder, then add just the changed files? or do I include all the version 1.0 files AND the new files into the 1.1 folder? Then go into wyBuild, redo the Build and Patch creation, then upload that to the server. (I tried that already and the build had some warning about not including the wyBuild.exe in the directory since it self-updates, but was built anyway.)
This is where it gets confusing.. since I have wyUpdate.exe already in my main app directory, if I build a new one for a patch, how does that get back to the user app directory so they can click on the 'check updates' button to trigger the patch process (and pull down the new version 1.1 files)? I am not wanting to have to re-run the Actual Installer program to generate a new setup.exe and have them reinstall our launcher every time. The point of a launcher is to click the button and check for patches for the main app. I would only rebuild the launcher if we have changes to the launcher itself. But the video makes it sound like we have to repackage all this into a new 'installer' every time.
So given ALL this, which way should I build this?
Thanks!Bill R
