Adding features via add/remove after a patch release

[tj]

Consider this scenario:

1. User installs via a setup.exe but is not licnsed for all features.
2. A patch released and installed via automatic updates. (remember no files exist for the omited features)
3. User purchases all features.
4. User uses add/remove from original setup.exe to install new features.

What will happen with the patch that was already applied? I'm guessing we would have missed the installation of the updates to the features that weren't originally installed? It seems as though the patch would not be run again because it was already applied once.

Thanks for your input in advance.

FYI - I am nearing the end of a complicated installation. I plan to go back and update all of my forum posts with my final solutions. This forum has been an extremely valuable suppliment to the documentation.

[tj]

To follow up on my original post...

It is my understanding that the patch would have upgraded the cached installation files (at least for web installations) and the patch would have actually updated the component not yet installed.

[MichaelNesmith]

Your assumption is wrong, while it would be great in theory, the original MSI has specific references (hashes, file sizes) to the original files that were installed, so this won't work.

Therefore just like an OS service pack application, any time the original installer is run, the patch will need to be applied again.