Shell Extensions
The following are limitations in the current Alchemy offering regarding packaging and virtualisation of Windows Shell Extensions. This includes features such as context menus and file associations. If any of the following scenarios are encountered, contact Cloudhouse for assistance finding a workaround.
1 - Background handlers are not virtualised correctly
It is possible to create shell extensions to handle right clicks in the background of a directory or drive. These appear in the registry at the following locations:
HKEY_CLASSES_ROOT\Directory\background HKEY_CLASSES_ROOT\Drive\background HKEY_CLASSES_ROOT\Folder\background
These shell extensions are captured by the Auto Packager but they are not automatically virtualised, meaning they will not function when the Alchemy Compatibility Package is deployed.
2 - File associations that use OpenWithProgIds are not virtualised correctly
When configuring a particular file type to open with a default program such that double-clicking on any file of that type automatically opens in the default program, one of the available ways to do this is by using the OpenWithProgIds registry key (provided a higher priority approach is not used). These OpenWithProgIds registry entries are not automatically virtualised by Auto Packager, so they will not function when the Alchemy Compatibility Package is deployed.
3 - Cloudhouse logo is displayed instead of virtualised app logo for associated file types
There are various ways of specifying both the application to associate with given file types and the icon that should be used when representing this association in Windows Explorer. When certain approaches are used and an icon is not specified, then the Cloudhouse logo will be used instead. The file association itself will work, and the file type will automatically open in the virtualised application.
4 - Cloudhouse logo and Cloudhouse Run text are displayed in Open With menu instead of the virtualised application
The Open With list available in the right-click context menu will always contain the Cloudhouse Run application instead of the virtualised application. Selecting this option will open the requested file system entry in the virtualised application.
5 - Virtualised application is not present in the "Open With -> Always use this app" menu
Currently, you are not able to designate a virtualised application as the default program for opening certain file types. When accessing the right-click context menu, you will not be able to select the virtualised application from the Open With > Always use this app option.
6 - Not all shell extension types are supported
There are many different kinds of shell extensions available in Windows, but not all are supported by Alchemy. Only context menu handlers and file associations are supported, with the exceptions listed above.