Skip to content

Order of Operations

Cloudhouse Alchemy performs various operations depending on which task it is performing on the Compatibility Package:

For more information on each of the components that are deployed or uninstalled, see: Configuring an Alchemy Compatibility Package.

Deploying in User/Machine Mode

When deploying an Alchemy Compatibility Package in user or machine mode, the following actions are performed:

  1. PreDeploy Event is executed.
  2. Compatibility Package is validated.
  3. ProgData files are copied over into the deployed folder.
  4. All Compatibility Package configuration files are copied to the deployed folder.
  5. AAV binaries are copied over into the deployed folder.
  6. The Pre-deployment script is executed.
  7. Windows add/remove program entry is set up.
  8. COM is deployed.
  9. COM+ is deployed.
  10. Shortcuts are configured.
  11. Services are installed (only in machine mode).
  12. Drivers are installed (only in machine mode).
  13. Post-deployment script is executed.
  14. Context menus are installed.
  15. File associations are installed.
  16. PostDeploy Event is executed.

Deploying in a Shared Context

When deploying an Alchemy Compatibility Package in a shared context (either a machine or user deploy), the following actions are performed:

  1. PreDeploy Event is executed.
  2. Compatibility Package is validated.
  3. Deployment Script is copied to the shared location.
  4. Com confirmation files are copied to the shared location.
  5. File associations file is copied to the shared location.
  6. App Registry file is copied to the shared location.
  7. Services file is copied to the shared location.
  8. Drivers file is copied to the shared location.
  9. Shortcuts file is copied to the shared location.
  10. The Pre-deployment script is executed.
  11. Windows add/remove program entry is set up.
  12. COM is deployed.
  13. COM+ is deployed.
  14. Shortcuts are configured.
  15. Services are installed (only in machine mode).
  16. Drivers are installed (only in machine mode).
  17. Post-deployment script is executed.
  18. Context menus are installed.
  19. File associations are installed.
  20. PostDeploy is executed.

Registering

When a compatibility package was not registered at deploy time, the following actions are performed when registering:

  1. PreRegistration Event is executed.
  2. Package is validated (inc. licensing)
  3. Files copied to user location
  4. Shorcuts are configured in user mode.
  5. Context menus are installed in user mode.
  6. File associations are installed in user mode.
  7. PostRegistration Event is executed.

Running in User/Machine Mode in a Shared/Non-Shared Context

When running an Alchemy Compatibility Package in user or machine mode in a shared or a non-shared context, the following actions are performed:

  1. Environment Variables are set.
  2. PreRun Event is executed.
  3. Package is validated (including licensing).
  4. App registry keys are deployed.
  5. COM keys are deployed.
  6. Log if services are not running.

  7. Run Programs. For each program:

    1. PreProgramRun Event is executed. (Ignored for services.)
    2. PostProgramRun Event is executed. (Ignored for services.)
    3. PostProgramStop Event is executed. (Ignored for services.)

  8. PostRun Event is executed.

Updating in User/Machine Mode

When updating an Alchemy Compatibility Package in user or machine mode, the following actions are performed:

  1. Compatibility Package is validated.
  2. Pre-uninstall script is executed.
  3. COM is uninstalled.
  4. COM+ is uninstalled.
  5. Shortcuts are removed.
  6. Services are removed (only in machine mode).
  7. Drivers are removed (only in machine mode).
  8. File associations are uninstalled.
  9. Post-Deployment script is executed.
  10. Windows installer/uninstaller is removed.
  11. All files are removed from the deploy folder.
  12. All registry entries are removed from the Cloudhouse root hive for all users.
  13. ProgData files are copied into the deployed folder.
  14. Compatibility Package configuration files are copied into the deployed folder.
  15. AAV binaries are copied into the deployed folder.
  16. The Pre-deployment script is executed.
  17. Windows add/remove program entry is set up.
  18. COM is deployed.
  19. COM+ is deployed.
  20. Shortcuts are configured.
  21. Services are installed (only in machine mode).
  22. Drivers are installed (only in machine mode).
  23. Post-deployment script is executed.
  24. Context menus are installed.
  25. File associations are installed.

Updating in a Shared Context

When updating an Alchemy Compatibility Package in a shared context (either a machine or user deploy), the following actions are performed:

  1. Compatibility Package is validated.
  2. Pre-uninstall script is executed.
  3. COM is uninstalled.
  4. COM+ is uninstalled.
  5. Shortcuts are removed.
  6. Services are removed (only in machine mode).
  7. Drivers are removed (only in machine mode).
  8. File associations are uninstalled.
  9. Post-Deployment script is executed.
  10. Windows installer/uninstaller is removed.
  11. All files are removed from the deploy folder.
  12. All registry entries are removed from the Cloudhouse root hive for all users.
  13. Deployment Script is copied to the shared location.
  14. Com confirmation files are copied to the shared location.
  15. File associations file is copied to the shared location.
  16. App Registry file is copied to the shared location.
  17. Services file is copied to the shared location.
  18. Shortcuts file is copied to the shared location.
  19. The Pre-deployment script is executed.
  20. Windows add/remove program entry is set up.
  21. COM is deployed.
  22. COM+ is deployed.
  23. Shortcuts are configured.
  24. Services are installed (only in machine mode).
  25. Drivers are installed (only in machine mode).
  26. Post-deployment script is executed.
  27. Context menus are installed.
  28. File associations are installed.

Uninstalling in User/Machine Mode in a Shared/Non-Shared Context

When uninstalling an Alchemy Compatibility Package in user or machine mode in a shared or a non-shared context, the following actions are performed:

  1. Pre-uninstall script is executed.
  2. COM is uninstalled.
  3. COM+ is uninstalled.
  4. Shortcuts are removed.
  5. Services are removed (only in machine mode).
  6. Drivers are removed (only in machine mode).
  7. File associations are uninstalled.
  8. Post-uninstall script is executed.
  9. Windows add/remove program entry is removed.
  10. All files are removed from the deploy/shared folder.
  11. All registry entries are removed from the Cloudhouse root hive for all users.

Unregistering

When a compatibility package was registered using the registration workflow, the following actions are performed when unregistering:

  1. Pre-unregistration Event is executed.
  2. Shortcuts are removed.
  3. Context menus are uninstalled.
  4. File associations are uninstalled.
  5. All files are removed from the user's directory.
  6. All registry entries are removed from the current user's Cloudhouse root hive.
  7. Post-unregistration Event is executed.