Introduction
This article presents a practical example of a Shell Extension that I've recently implemented. I was showing travel photos to friends, and I wanted to show only the best photos in my folders. One possible solution was to use one of the great photo managers around but I wanted to work directly with the standard Explorer interface.
The idea is really simple, add a new Rating column to the Folder View of Explorer under Windows XP. This new column can be used to sort the files (photos, MP3s ...) by the user defined rating and it works with the Photo Preview of Explorer, so I can show first the best photos. The side effect of this approach is that it is possible to sort the results of a Search by the Rating thus obtaining the best photos in a folder tree.
This is an example of the extended Explorer view:
and these are the new entries in the context menu:
Table Of Contents
- Shell Extensions - Overview, Debugging, Registration
- Implementation
- Improvements
- Conclusions
- References
The Windows Shell has a powerful extension mechanism that gives the possibility to provide new functionalities and interaction capabilities to the Shell. The implementation of these extensions in C++ and COM was quite difficult, but a lot has changed with the introduction of .NET. (In the References section, I've reported some links.)
This is a schema that explains the possible Shell Extensions that can be created and what is used by this article.
Debugging
The debugging of Shell Extension with .NET is the same as that of COM (see this). It's just necessary to specify the Explorer.exe as the executable for the debugging session and set to 1 the DesktopProcess
DWORD
value of the key.
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer
This value tells the Explorer to create a separate process for each window and one for the Taskbar, easing the debugging of the extension.
Registration
The registration process has an extension type specific part and the general part. The general part is mostly performed by the regasm.exe utility (invoked by VS.NET) that addresses all the COM-.NET connection. If the extension is intended to be installed on non-administrator accounts, it's important to register it under the Approved set of extensions:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved
It's sufficient to add a new string value to this key with the name as the curly braced GUID of the class and an optional description. To inspect the installed extension, there is the Autoruns utility by SysInternals.
The extension specific registration can be performed directly by managed code using two special attributes ComRegisterFunctionAttribute
and ComUnregisterFunctionAttribute
. The following snippet of code presents how to implement that for registering this extension.
#region Registration
[System.Runtime.InteropServices.ComRegisterFunctionAttribute()]
static void RegisterServer(String str1)
{
try
{
string keyname = "File Rating";
string guid = "{"+typeof(RatingColumnHandler).GUID.ToString()+"}";
RegistryKey rk,rk2;
rk = Registry.ClassesRoot.OpenSubKey(@"*\shellex\ContextMenuHandlers", true);
...
}
catch(Exception e)
{
}
}
[System.Runtime.InteropServices.ComUnregisterFunctionAttribute()]
static void UnregisterServer(String str1)
{
try
{
string keyname = "File Rating";
string guid = "{"+typeof(RatingColumnHandler).GUID.ToString()+"}";
RegistryKey rk;
rk = Registry.ClassesRoot.OpenSubKey(@"*\shellex\ContextMenuHandlers", true);
rk.DeleteSubKey(keyname, false);
...
}
catch(Exception e)
{
}
}
#endregion
The File Rating extension uses a Column Handler to add a new column to the Detailed view of Explorer, the column is registered for in the folders ("Folder/shellex/ColumnHandlers" in the registry's Classes root) and implemented through the interface IColumnProvider
. The values of the column can be used for sorting the files, also in the Preview mode of the Explorer.
I've decided to store the rating information of each folder into a .rating file where, in each line, there is the rating, a tab, and then the file name. This is the simplest solution, but there are some issues that I'll discuss in the future work. This file is cached by the Column Handler, and each time, it can be checked against changes using a timestamp.
The user can change the ratings by editing directly the .rating file or better by using a new entry in the Context Menu associated with every file ("*/shellex/ContextMenuHandlers" in the registry's Classes root). Two interfaces, IShellExtInit
and IContextMenu
are required for the correct implementation of this extension.
IShellExtInit
The method Initialize
of this interface is invoked when the extension is going to be invoked on a new folder, and it gives the occasion for obtaining the folder and the files involved in the operation. This operation is carried on by using some Clipboard and Drag&Drop relative functions, and it could be nicely wrapped in a helper class. The list of the files is saved during the initialization phase and used later during the menu construction and invocation (for changing the menu depending on the selection).
IContextMenu
This interface is used to obtain the effective menu for the selection of files involved in the operation (QueryContextMenu
) and to process the option selected by the user (InvokeCommand
). Optionally, it can provide to the Shell, help information (GetCommandString
).
The QueryContextMenu
answers to the question of the layout of the menu, and it requires some Win32 menu construction. Each entry is associated to an identifier that is passed to the InvokeCommand
when the user selects the menu entry. In this case, the menu is not dependent on the selection and it uses a submenu to group the options:
int IContextMenu.QueryContextMenu(HMenu hMenu, int iMenu,
int idCmdFirst, int idCmdLast, CMF uFlags)
{
int id = 1;
if ( (uFlags & (CMF.CMF_VERBSONLY|CMF.CMF_DEFAULTONLY|CMF.CMF_NOVERBS)) == 0 ||
(uFlags & CMF.CMF_EXPLORE) != 0)
{
HMenu submenu = ShellLib.Helpers.CreatePopupMenu();
Helpers.AppendMenu(submenu, MFMENU.MF_STRING|MFMENU.MF_ENABLED,
new IntPtr(idCmdFirst + id++), "Rating ++");
Helpers.AppendMenu(submenu, MFMENU.MF_STRING|MFMENU.MF_ENABLED,
new IntPtr(idCmdFirst + id++), "Rating --");
Helpers.AppendMenu(submenu, MFMENU.MF_STRING|MFMENU.MF_ENABLED,
new IntPtr(idCmdFirst + id++), "Zero Rating");
Helpers.AppendMenu(submenu, MFMENU.MF_STRING|MFMENU.MF_ENABLED,
new IntPtr(idCmdFirst + id++), "About");
Helpers.InsertMenu(hMenu, 5,
MFMENU.MF_BYPOSITION|MFMENU.MF_POPUP|MFMENU.MF_ENABLED,
submenu.handle, "File Rating");
}
return id;
}
There are some issues about this extension, but they don't really prevent its usage.
- In the case of read only folders, the .rating file solution is not applicable, and a centralized solution is better, but it would increase the complexity of this extension.
- When a file is renamed or moved, the rating information is lost; this could be addressed by using a FileWatcher on the folder, but it has the side effect.
- The solution of an additional hidden file in a folder is not nice, because there are too many. An alternative solution that also solves problem #2 is to use the NTFS extended properties. This is a feature of NTFS 5.0 that gives the opportunity to associate properties to file like Title, Category, and in this case, the Rating. In general, the file rating information could be stored inside the metadata information of a Metadata based file system.
- When the user changes the Rating by the context menu, the Explorer view is not updated, and it's required to do a refresh command. (Can anyone suggest me how to do this?)
- The rating information could be computed in some automatic way, by tracking file usage or other information, like it's performed by the latest Windows Media Player.
This short article presents here a practical example of shell extension that can be used to rate files like photos or audio files. I hope that it will be useful to someone.