Create Installer Package with launch conditions

[torrin47]

From @joeponcy on November 15, 2016 18:21

• [ ] Create installer UI

• [ ] Check prerequisites and dependencies ( .Net Framework & ArcGIS Version )

• [ ] Install prerequisites

• [ ] Install ArcCatalog components depending on version detected

• [ ] Include option to overwrite or preserve existing EMEdb files if found on system

• [ ] Check to see whether EME 3.2.1 is installed and notifying the user that it should be uninstalled

  • If possible: Include option to uninstall EME 3.2.1 (and removing problematic registry entries)

• [x] Include Python toolbox with EPA update metadata from FGDC script/xslt

The current stand-alone installers preserve existing files by default. This may be the best option as it requires the user to manually delete the db files if they need to be replaced, very unlikely to happen by accident. A flag in the current installer ensures that the files can be overwritten if we release an updated source file.

Copied from original issue: Innovate-Inc/EMEMetadataToolKit#68

[torrin47]

Couple of questions for ya. Since we know about synchronization issues involving EME 3.2.1, what is the feasibility of the following?

1. Checking to see whether EME 3.2.1 is installed and notifying the user that it should be uninstalled.
2. Checking to see whether EME 3.2.1 is installed and uninstalling EME 3.2.1 (and removing problematic registry entries)
3. Including Python toolbox with EPA update metadata from FGDC script/xslt.

[torrin47]

From @joeponcy on November 15, 2016 20:14

1. Is definitely doable May be possible.
2. I will look into it
3. Yes, we can include this as part of the installer package

[torrin47]

Never addressed in EME 5 (ArcCatalog deprecated). Not relevant in Pro as add-in doesn't require install.