I think I went a bit backwards on my update process. I used to be able to display incremental updates (More than 1 version release notes in the wyUpdate screen). I have a demo tomorrow and could use some help identifying how to get this back.
I've been testing with a project that has 3 different versions:1. 7.0.0.827 (Base Version)2. 7.0.5.33. 7.1.11.10
Versions 7.0.5.3 and 7.1.11.10 both have unique release notes and the application files referenced in all 3 versions are have their own version folder on disc. I made sure to delete all of the .wyu and .wys files in wyBuild output directory as well as on the web server where updates are retrieved. Here is the process I took to test this scenario was built:7.1.11.10 I built my wyUpdate client using the base version (7.0.0.827) and stored both the wyUpdate.exe and client.wyc files in the client application directory. 2. In wyBuild I then created the update from version 7.0.0.827 to 7.0.5.3 and uploaded it to our web server. 3. I ran the wyUpdate client to see that the release notes appeared without any issues for the 7.0.5.3 version. However, I didn't click the "Update" button at this point (So I can see the release notes display more than 1 version the next time around). I closed the wyUpdate application down to prepare for the next step.4. Once that was done I then created the update from version 7.0.5.3 to 7.1.11.10 and uploaded that the web server. *** At this point, things get interesting for me. ***5. I ran the wyUpdate client again and noticed that only the version release notes that appeared were for the latest version (7.1.11.10).
I then rolled back the wyBuild output files for both my local build server and the web server where the updates existed. I then created the update from version 7.0.0.827 to 7.1.11.10 to see if this changed anything, but got the same results. Any thoughts as to what could be preventing the individual version release notes from being displayed altogether?
I feel like I'm spinning my wheels here...
Jim
wyUpdate only shows the changelog of any versions the user doesn't have. So if the user is on 7.0.0.827 and you've released 7.0.5.3 and 7.1.11.10, then the user will see the changes from both 7.0.5.3 and 7.1.11.10.
If the user is on 7.0.5.3 then they'll only see the changes for 7.1.11.10.
Does that make sense?
It absolutely makes sense, but the fact that my client listed the original version (7.0.0.827) in the header and the notes below only listed the latest version (7.1.11.10) it baffled me. However, just before my demo I recompiled the entire media from start to finish rather than compiling each jump in versions individually and it worked (e.g. 7.0.0.827 to 7.0.5.3 and 7.0.5.3 to 7.1.11.10). I certainly know I've covered this step before.
These ghosts were getting me nervous, but I'm sure you'll write it off as missing a step. I'm confident that I was following this to a T. I feel this is like me calling "Tech Support" and once they get there things work 🙁 lol.
I guess, one thing that I could use some clarification on is if I recompile from start to finish or compile each version jump individually would this still create the same outcome if a client hasn't received these updates (Other than the 1st version, of course)?
Jim
I guess, one thing that I could use some clarification on is if I recompile from start to finish or compile each version jump individually would this still create the same outcome if a client hasn't received these updates (Other than the 1st version, of course)?
We don'y have direct patches (A->B, B->C, C->D) yet. That's coming soon. Right now wyBuild just builds direct patches (A->D, B->D, C-D).
So you have to build updates from the oldest version to the newest version.
Wyatt,
Sorry for the delay... I eventually just went with recompiling everything and it's working as expected consistently.
Thank you for the clarification.
Jim
