Opened 11 years ago

Closed 11 years ago

#193 closed Bug (fixed)

AutoUpdate and MSI install compete against each other

Reported by: Matthäus Wander Owned by: sauer
Priority: Important Milestone: CrypTool 2.0 BETA 4
Component: AutoUpdate Keywords:
Cc: Arno Wacker, marchal


You need three different CT2 builds to reproduce this issue: v1, v2, v3

  • Install CT2 v1 from MSI (use default installation path)
  • Use AutoUpdate to install new version v2
  • Install newer version CT2 v3 from MSI (use default installation path)

Expected: One CT2 installation with v3.

Actual: I get one CT2 folder with v3, but two desktop links, one with v1 and one with v3. Both, v1 and v3 are in my "Programs" control panel (Windows system control). If I choose to uninstall v1 it works, but it deletes half of the files in the installation folder (those whose assembly version did not change between v1 and v3, i.e. AppReferences). The CT2 v3 installation is thus broken and fails to start.

I would plead strongly to use either one installation/update mechanism: either we rely completely on MSI or we build it completely manually (with Zip and self-build installation scripts, but not MSI). Using both mechanisms does not work well together.

Change History (3)

comment:1 Changed 11 years ago by Matthäus Wander

Plus, MSI setup does not update files which have been modified by the user or by v2 .zip AutoUpdate. Therefore any MSI setup installation after performing a .zip AutoUpdate will not work correctly.

Arno's hint to use "silent MSI update":

comment:2 Changed 11 years ago by Matthäus Wander

Cc: Arno Wacker marchal added
Keywords: wacker marchal removed

comment:3 Changed 11 years ago by Matthäus Wander

Resolution: fixed
Status: newclosed

MSI Update has been implemented (thanks, Simone). May require a revision when new NSIS installer becomes active, however the MSI-related issue is fixed.

Note: See TracTickets for help on using tickets.