Ticket #782 (closed assessed: fixed)

Opened 8 years ago

Last modified 6 years ago

Plug-in auto update logic does not detect new releases of the same version number

Reported by: jeroens Owned by: jeroens
Priority: normal Milestone: Ecopath 6: release 6.3 BETA
Component: Overall Plugins Version:
Severity: tweak Keywords: plug in, auto update
Cc:

Description

The auto-update logic is still rather crude, detecting only whether the assembly version number of a plug-in matches that of the installed EwE6 Scientific Interface. This prohibits bug fixes of a plug-in to be adequately detected and installed.

By extending the plug-in update logic to also consider a file version flag we this limitation would be solved.

Change History

comment:1 Changed 8 years ago by jeroens

  • Milestone changed from Ecopath 6: release 6.1.1 to Ecopath 6: release 6.2

comment:2 Changed 7 years ago by jeroens

  • Milestone changed from Ecopath 6: release 6.2 to Ecopath 6: release 6.3

Had not yet the time to cater to this. Is tentatively scheduled for release w Ecospace packages

comment:3 Changed 7 years ago by jeroens

Simple solution:

Use three digits for versioning rather than 4, and reserve last digit for revision information. Changes are needed in EwERenameAssemblies (to preserve file version), update checker (to check for latest revision for a version for any version newer than a given release), automated builds (to issue new format of version number) and plugin compatibility checks.

.NET assumes a revision number in the last digit; this should not impede current plugin strategy.

Version 0, edited 7 years ago by jeroens (next)

comment:4 Changed 6 years ago by jeroens

  • Status changed from new to closed
  • Resolution set to fixed

Fixed

Note: See TracTickets for help on using tickets.