Updating a Designer Project To a Newer Version Of The Plugin It Uses

Cognex Designer plugins follow the Semantic Versioning rules (see Plugin and Versioning Guidelines), so it is possible to automatically update to the highest Minor version (Major.Minor.Patch) without breaking the project. Designer always prompts the user before making any changes.

If a project encounters a new plugin that has a higher compatible version, then Designer asks the users if they wish to upgrade.
If a higher Major version is available, Designer displays it as a possible option but does not select it automatically. If the user selects this version and clicks Apply, a warning message appears.
If the plugin is missing, Designer lets the user choose an alternative.
An update question is asked once. The next time Designer will ask about the same plugin is when an even newer version becomes available. Consider this scenario:
1. The user creates a project using version 1.5.3 of a Test Plugin.
2. Versions 1.5.6 and 1.7.3 are installed.
3. The user starts the project and selects version 1.5.6
4. The next time the user launches the project, there will be no questions as no newer versions have been installed.
5. Version 1.5.9 is installed.
6. The user starts the project and gets a dialog with 1.5.9 and 1.7.3 as upgrade options.