| 6 | | Originally (versions 3.0, 3.1, 3.2) , it was possible to dynamically update all or selected plugins dynamically using the plugin infrastructure. For this we hosted an update service that provided meta-information and binaries of plugins. This functionality is however not supported anymore, therefore all the code for dynamic updating can be removed. We decided that plugin updating is not necessary. Instead, users should just download the whole HeuristicLab package whenever a new version is released. |
| | 6 | Originally (versions 3.0, 3.1, 3.2) , it was possible to update all or selected plugins dynamically using the plugin infrastructure. For this we hosted an update service that provided meta-information and binaries of plugins. This functionality is however not supported anymore. Therefore, all the code for dynamic updating can be removed. We decided that plugin updating is not necessary. Instead, users should just download the whole HeuristicLab package whenever a new version is released. |
| | 7 | |
| | 8 | We discussed the idea that a small component could check and download new updated assemblies from our website and install them after restarting the application. |
