Content View By File Type or Kind
This topic describes a new view in Windows Explorer, called the Content view, that displays the most relevant content for each item. Using a set of registry keys, items can define a property list and a layout that the Shell uses for Content view. The Shell retrieves the registry keys by using the item's association array.
How Does the Content View Work?
In Windows 7 and later, the Content view uses a resizing logic that drops properties when the window size decreases, to ensure that the most critical properties still have room to be clearly readable. The following screen shot illustrates the Content view of search results containing music, pictures, and documents.
Some Shell data sources use Content view by default, but users can select the Content view by clicking the View Control button in Windows Explorer. A Shell data source extends the Shell namespace and exposes items in a data store. The items in a data store can be indexed by the Windows Search system using a protocol handler.
How to Implement the Content View
When registering a new file type or protocol handler, you can take advantage of the Content view by using either of two different approaches. You can use an existing set of properties and layout pattern, or you can create your own combination.
You can use a registry entry to associate your file type or item with a predefined Kind, which is a property that you can think of as a content category. By associating your file type or item with certain of these Kinds, you automatically inherit that Kind's Content view layout patterns and property lists. Windows defines Content view layout patterns and property lists for the following Kinds: documents, email, folder, music, picture, and generic. This type of association is encouraged. It lets you provide the consistent experience that a user expects for similar items.
For more information, see File Types and Kind Names and How To Register a Unique Content View Set of Properties and Layout Pattern for the File Type or Item.
Additional Resources
- For property reference documentation, see System.Kind, and System.KindText.
- For PropList reference documentation, see System.PropList.ContentViewModeForBrowse, and System.PropList.ContentViewModeForSearch.
Related topics
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for