You can include any files your want with wyBuild and it will gladly build the patch. If that strategy works best for you, then do it. The more typical strategy is to release the update and if there are bugs or regressions, then release another update to fix those bugs.
Including a 'safe' version of my software with wyBuild
lmondelloAlthough it is hard to believe, I will occasionally release a version of my software with a show-stopping bug. 🤣
My software is a plugin distributed as a .dll
I was thinking of including a 'safe' version of my software, which would basically be the last released version that I would copy into the wyBuild folder of the new version, but renamed like so:
Last released version:
MyPlugin16.4.dll <------- version 16.4.2256.22200
New release:
MyPlugin16.4.dll <----------version 16.4.3252.19650MyPlugin16.4.dll(safe) <------------version 16.4.2256.22200
This way if things go teats up, my users would be able to delete the new version and manually rename MyPlugin.16.4.dll(safe) to MyPlugin16.4.dll so at least they can be up and running with that last good version that they had just had working..
A wyBuild rollback feature would be nice, but with some updates of my software rolling back to a previous version would not be trivial, since my plugin can update our MySQL tables from time to time, so all those database table changes would have to be rolled back as well.
Any comments/suggestions on my strategy?