Let's say I have an initial install of my software of version 1.1.1. I now want to create version 1.1.2. Can I use the initial project to do this or do I need to create a new project? Can I use the initial versions (1.1.1) project to add some new .sql scripts and update my programming code and change the project version to 1.1.2? Can I use this project to create an install package for version 1.1.2 and also a patch that will update version 1.1.1? How would I do this and what would be the steps, or is this possible? Would the product code change or need to change? What about the Upgrade Code?
The world of Windows Installer upgrade rules can be a confusing one - and the topic is quite large so you will need to be prepared to commit to some learning.
We have 3 great videos which explain the concepts of upgrades and how to create them here - the "Introduction..." video in particular should answer your questions.
I'm sorry you're having some audio issues - I've just tested this and I'm not hearing any issues, the audio was available throughout the video. Please try watching it via the youtube link: https://www.youtube.com/watch?v=70Fzvtt18GU&t=168s
Sorry my speaker cord came loose. So if I understand this correctly, If you have a base project and add a patch, if you do a build it will create an install package for version 1.1.2 with a Setup.exe. Then you go to the Patch design set necessary settings, and click the build Patch button and it will create a Patch to update version 1.1.1 to 1.1.2? Is this correct?
A patch is just another way of delivering a Minor Upgrade - to create one you will need: 1. The Base Install 2. A Minor Upgrade Install created from the base Install 3. You can then use "Patch Design" in your project to point to the previous (base) and latest (Minor Upgrade) installs and then click "build patch"
I'd strongly recommend that you test the Minor Upgrade successfully upgrades the package correctly before you create the patch in case there are any issues.
