In wyBuild 2.7.x (probably 2.7.0) we're adding a "what's changed" link when you build your updates. This will list everything that has changes in the updates (files added, ignored, patched, deleted, etc.).
First off, I demoed the trial of wyBuild and purchased it within hours, I was that impressed, great stuff.
I was wondering if it would be possible to include some sort of sanity check into wyBuild. I am mostly thinking of "missing" files that if a user updated before the omission was caught, would ultimately cause the application to be non-functional . I realize a "fix" update could be posted and manually retrieved using wyUpdate.exe, but in a multiple, remote deployment scenario, it becomes cumbersome. I also realize that the ultimate "fix" is to not miss any files in the first place, but sadly, I'm encumbered with humanity.
I am thinking of something as simple as a warning "the previous version of this application included files x,y,z which are not included in this version, is this correct?" I don't know that additional files matter as much as omitted files. It would also only have to be compared from the version immediately previous to the new one being built; theoretically, if this check is done at each new version to the immediately previous version it should provide continuity all the way through.
In wyBuild 2.7.x (probably 2.7.0) we're adding a "what's changed" link when you build your updates. This will list everything that has changes in the updates (files added, ignored, patched, deleted, etc.).