Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Specifying a Namespace Extension's Location

The root of a namespace extension is normally displayed by Microsoft Windows Explorer as a folder in both tree and folder views. For Windows Explorer to display your extension's files and subfolders, you must specify where the root folder is located in the Shell namespace hierarchy. This location is referred to as a junction point.

Using Virtual Folders as Junction Points

The simplest way to define an extension's junction point is to make the root folder a subfolder of a system virtual folder. This type of junction point is referred to as a virtual junction point. The Desktop and My Computer folders are the typical locations for virtual junction points, but you can also define a virtual junction point on a remote computer or under the My Network Places, Internet Explorer, and Control Panel folders.

To define a virtual junction point, create a subkey of the key that represents the appropriate virtual folder and name it with the string form of your extension's class identifier (CLSID). The registered CLSID would appear as follows.

    • Software
      • Microsoft
        • Windows
          • CurrentVersion
            • Explorer
              • Virtual Folder Name
                • Namespace
                  • {Extension CLSID}

Virtual Folder Name is one of the registry key names in the following table.

Location Virtual Folder Name
My Computer MyComputer
Desktop Desktop
Control Panel ControlPanel
My Network Places NetworkNeighborhood
Entire Network NetworkNeighborhood\EntireNetwork
Remote Computer RemoteComputer

Remote extensions must be initialized with IRemoteComputer.

Note  You can also define junction points on a per-user basis by registering them in the equivalent location under the HKEY_CURRENT_USER key.

Using File System Folders as Junction Points

There are two ways to define file system folders as junction points. The simplest approach is to create a folder in the appropriate location and append a period to the folder's name, followed by the string form of the CLSID of your extension. Only the folder name will be visible in Windows Explorer. The following example creates a junction point with a display name of MyFolder.

MyFolder.{Extension CLSID}

Alternatively, you can define a conventionally named folder as a junction point by:

  • Making the folder read-only.
  • Making the folder a system folder by calling PathMakeSystemFolder.
  • Placing a hidden Desktop.ini file in the folder that includes the extension's CLSID.

Desktop.ini is a standard text file that can be added to any folder to customize certain aspects of the folder's behavior. For a general discussion of how to use this file, see Customizing Folders with Desktop.ini. To define a folder as a junction point, the [.ShellClassInfo] section of Desktop.ini must contain the extension's CLSID as follows:

CLSID={Extension CLSID}

Opening a View of a Namespace Extension

When a user browses into a junction point, Windows Explorer automatically creates a view of the root folder. You can also create a view by explicitly launching Explorer.exe with the extension's CLSID as an argument. You can, for instance, use this approach to launch a view of an extension from a shortcut menu or shortcut. For example, to launch a view of MyExtension that includes a tree view, you can use the following command string.

%SystemRoot%\Explorer.exe /e,::{MyExtension CLSID}

An alternative command string can be used to launch a view of an object within the extension. This feature would be useful, for instance, for an extension that uses a folder view to allow users to view the contents of one of a number of compressed files.

%SystemRoot%\Explorer.exe /e,::{MyExtension CLSID},objectname

The objectname parameter is the name of the object that is to be viewed. Windows Explorer converts the name to its corresponding PIDL and passes the PIDL to the new folder object's err! bad xref: _win32_IPersistFolder_Initialize [ambiguous xref; must specify @autoiid, @iid, or @primary.] method.

Note  The CLSID string must be preceded by a pair of colons (::) or the command will fail. The slash-e (/e) flag used in the two sample command lines shown previously instructs Windows Explorer to display a tree view. The flag must be separated from the two colons by a comma. If you do not want a tree view, omit the /e flag and the comma.

Community Additions

© 2015 Microsoft