Hey
Ive had various threads regarding updates, each one with a specific topical direction. Ive also been through your help files and while i appreciate they are helpful, each help file is specific to its content and i cant really find anything that explains in detail a way to create an initial installer followed up by a update process, So, would you please be able to add or at least respond here with a systematic breakdown of how one should create then manage an install file through its lifecycle as a typical or best practice?
1. First time Install
2. Update. Patch, Upgrade or a new build event?
3. Should we save an install project file for every iteration of new version
etc
This is how i would define
Install - a file that will install the latest version. for example, the first time advanced installer has ever been installed
patch - a file to repair your current version without changing your assembly version. for example, updating a faulty library reference
update - a file that will change your latest installed version to the latest version while keeping any existing settings. for example, 18.0 to 18.5
upgrade - a file that will change the options of the install. for example, Advanced installer from Architect to enterprise, both on the same 18.5
So
If im working with assembly iterations, i would assume an update. That update would contain all of the install files required and be made available to any new user.
If im offering different version types that provided different features, that upgrade would contain a way to differentiate those options within the same assembly version. All upgrades would be within the same assembly version
If there was a small issue that needed a band aid or 'patching up', i would make a patch to fix it within that assembly version
Would i then, be looking at making updates using the same build installer with all files and generating a new product code each time?
Would i need to save each minor version as a new installer copy of the build project?
Thanks