Version 1.0.beta

Runtime Machinery
Software Development Kit
Source Documents
Additional Samples

Release Notes

Changes from v0.8.0:
  • The Manager and Executor can both now run in two modes:
    • as a normal desktop application
    • as a windows service
  • The Service mode includes a GUI Service controller, which looks exactly like the desktop application version. This can be used to start/stop the service and change the settings for the Manager/Executor. The Services are configured to startup automatically by default. This can be changed using the standard Windows Service Control Manager. Note: The Executor works only in the dedicated-mode while running as a service.
  • The Manager and Executor have advanced logging capabilities enabling easier reporting of errors. The logging is enabled by default, and uses the log4net APIs. This includes detailed debug information which is useful while tracking possible bugs. The logging settings cab ne changed using the Alchemi.Manager.exe.config for the Manager and the Alchemi.Executor.exe.config file for the Executor. The Manager produces the log file: alchemi-manager.log while the Executor logs its information in alchemi-executor.log.
  • The Manager and Executor have the capability to automatically update themselves. The update process is actuated manually by the user via the "Help > Check for updates" menu option. This begins the update process with the Manager/Executor checking for updates from a predefined location. The update process is described in detail in the documentation.
  • The Executor can now detect if a Manager is disconnected and this launches a seperate thread to try and connect to the manager again.
  • The Executor Heart-beat and other additional connection settings (such as those which define parameters for actions when a Manager is disconnected) are configurable through the Executor form.
  • The GApplication now cleans up files properly after completion.
  • A new constructor in the GApplication class defines if it can be re-used. By default a GApplication is only single use.
  • Added a new method to ThreadCollection to enable removing threads from the application. This API feature is under review, and is not guaranteed to remain unchanged in the stable v.1.0.
Breaking Changes:
  • A new namespace Alchemi.Core.Owner has been introduced and the following classes have been re-arranged to be part of this namespace:
    • ApplicationState
    • EmbeddedFileDependency
    • FileDependency
    • FileDepenedencyCollection
    • GApplication
    • GConnection
    • GConnectionDialog
    • GConnectionDialogForm
    • GJob
    • GThread
    • ModuleDependency
    • ThreadCollection
    • ThreadIdentifier
    • ThreadState