Idea on a more robust uninstaller business logic for the icon editor VI package

[svelderrainruiz]

Problem statement

When a user installs the icon editor VI package, there is an edge case where the backup that was made to install the new icon editor could be erased, leaving the user on a situation where he can lock himself out of having a shipping icon editor, and the only solution for this is to know exactly which files to copy over from another LabVIEW installation, or to reinstall their copy of LabVIEW.

This creates a problem for new users of this new installation mechanism since it adds a layer of uncertainty whether they need to quarantine the package by using a VM.

Proposed solution

Create combination of backups for all LabVIEW versions and bitnesses and have that as part of our icon editor repo. Have a pre build action that would select the correct backup depending on the LabVIEW version that the VI Package is currently being built on.

This way it makes it very unlikely for a user to be locked out from user its icon editor, and would have to do something much more intentional to lock himself out (and even this has a solution by installing and uninstalling the package, to trigger the uninstall logic that restores the shipping icon editor).

This also allows for the VI Package to be smaller, because we are only including backups that are specific to the LabVIEW version we are trying to build.