MarekOur current wyUpdate integration is as follows:
1 create a new product version within wyBuild and describe changes that were done2 click "Build wyUpdate" within wyBuild to build wyUpdate.exe and client.wyc3 compile the wix setupThe setup generator script gathers all files that will be included in the MSI package, including wyUpdate.exe and client.wyc.The installer builds a MSI package for "from the scratch installations" from these gathered files. These installations include the client.wyc file.
I manually take all the gathered files and drop them into the newly created version in "Files & Folders" section within wyBuild. Then I build updates and send them to the client to upload them via FTP.
Everything seems to work fine when done this way.
My concern is that the "Your program's folder" files are dropped into wyBuild after I have built the client.wyc file and these files contain the client.wyc file. My tests showed that client.wyc is modified with every build, but this may have a different reason.
Is it correct to first build client.wyc, then gather all required files including client.wyc and only then include the files in "Files & Folders" section in wyBuild?
Does client.wyc include any information about the installed files themselves?
Better yet for documentation purposes, can you specify all the information that is contained in client.wyc file?
Otherwise, we would fight a serious chicken vs. egg syndrome here 🙂
All great questions. We've just now added a FAQ help file. The "What does the client.wyc file contain" question in particular should help you.
Your build steps look fine. And the client.wyc file does change everytime you rebuild it. The reason is that the new version is embedded in the file. You can choose to include the file in your updates or not.
