Well i need some guidance about patch/upgrade operations. If these questions are not AI related, any direction you can point me will be enough.
Question One;
As i understand in order to have a patch i must have from and to MSI packages. I am currently using Bootstrapper and no MSI packages are created, even if i click "Do not delete extracted MSI and CAB files" i don't see an .msi file. Is file created else where or it is created during installation and not removed?
Question Two;
Even if i make a very minor change and build setup package it needs to be un-installed and re-installed. What is the default approach/Best Practice for this? I mean i use a folder named "Product Name" and inside i have all necessary files. When we release a build, and make modifications after that what should i do? Use another folder "Product Name v.xx" or i should update the previous one? And in order to have the ability for a patch i must keep all of my setup releases, so every .msi file we have published i should keep them, or at least the last one.
Question Three;
I think, any change that requires a new build means a new version. So i must edit version but keep the original Product Code for patching, or a new code for upgrading. How should i decide if this is a patch or upgrade. Any standards such as Bug/Hot Fixes are patches and functinality changes are upgrades?
These questions are probably my lack of knowledge about versioning + release management.
As i have said, even if these issues are not AI questions, any direction you can lead me or any keywords to search will help me a lot. I did read about Creating Patches, Patch Projects and a sample patch project on your guides.
Thank you.
can
FOLLOW US
Get the latest news in Application Packaging