|
Structure of Registry Entries
The following registry structure is required for Quick View to associate a
class identifier or filename extension with the class identifier of a file viewer.
HKEY_CLASSES_ROOT
\QuickView
\<extension> = <human-readable document type>
\{<CLSID>} = <human-readable viewer name>
\{<CLSID>} = <human-readable viewer name>
\{<CLSID>} = <human-readable viewer name>
...[More extension entries for additional file types]
...
\CLSID
\{<CLSID>} = <human-readable viewer name>
\InprocServer32 = <full path to file viewer DLL>
= ThreadingModel = "Apartment"
...[More class IDs for file viewers and other object servers]
A description of the registry entries follows.
Entry
| Description
| HKEY_CLASSES_ROOT
| Root of the registry.
| QuickView
| Top-level key under which associations are stored.
| CLSID
| 16-byte OLE class identifier spelled out in hexadecimal digits in the form of
12345678-1234-1234-1234-1234567890AB with the hyphens included. All class
identifiers are surrounded by curly braces when stored in the registry.
| human-readable document type
| String describing the file type associated with the class identifier or
filename extension that can be displayed to the user. A file viewer can change the
type when it is installed so that the name always reflects the preferred viewer.
For example, this string might be "Windows Write Document."
| human-readable viewer name
| String that describes the vendor of the file viewer, as it might be displayed
in an About box, such as "Company ABC Write Document Viewer."
| <extension>
| Three-character filename extension with the period, as is consistent with the
standard 8.3 filename format for example, .WRI.
|
CLSID and InprocServer32 are standard OLE (32-bit) subkey names. The "ThreadingModel = Apartment"
entry is required for file viewers. The apartment threading model, which is new for
OLE in Windows 95 and Microsoft® Windows NT® version 3.51, allows the OleInitialize and CoInitialize functions to be called from multiple threads.
The QuickView key can have any number of filename extension subkeys, each representing a
registered file type. Each filename extension subkey can have one or more class
identifier subkeys, each representing a registered file viewer object. The most
recently registered file viewer appears first in the list of class identifier
subkeys, and it is the first one found when Quick View enumerates the registered
file viewers.
Note The file viewer class identifier should always differ from the file type
class identifier because the application that created the file may already be
using the class identifier to identify the application as a compound document
server.
Each class identifier stored under the filename extension subkeys must
correspond to an entry of the same class identifier stored under the top-level key
called CLSID. This is the standard location for storing information for OLE object
servers. For file viewers, there must be an InprocServer32 subkey under the file viewer's class identifier key. The value of the InprocServer32 subkey is the full path to the file viewer DLL. You should store the full
path and not depend on the DLL being in the path of the Windows 95 environment. InprocServer32 is a standard OLE subkey where the path to a component object server is
stored. Using this subkey allows the Quick View program to use standard OLE member
functions to access and create objects from file viewer servers.
| Last news from Greatis Software |
 |
|
Nostalgia .Net |
|
.Net is powerful, but not all-powerful, so sometimes we need to use Win32 API for our .Net applications. It's simple enough with Platform Invoke if you have Win32 skill, but we do not always have time to dig the ancient documentation, declare the special types that are compatible with Win32, find the values of the Win32's constants and so on. Nostalgia .Net offers several simple-to-use classes, and components that will allow you to forget about the headache of Win32 and just use the power of Win32 in your application the same way as you use the native. Net classes. More » |
| Recommended software for developers |
 |
|
Ultimate Pack |
|
Component pack for Delphi and C++ Builder that contains runtime form designer, runtime object inspector, print suite and much more for the very special price. More » |
 |
|
Form Designer .Net |
|
Unique runtime form design solution that allows to edit any form in .Net WinForms application at runtime with full source codes for only 300 euro! More » |
 |
|
Print Suite .Net |
|
Print Suite .Net is a set of components for easy printing texts, images and grids from your WinForms applications. Full C# source codes are available More » |
 |
|
Gradient Controls .Net |
|
Gradient Controls .Net offers controls with gradient background feature. Labels, panels and so on... Full C# source codes are available More » |
 |
|
Greatis iGrid |
|
iGrid plots drawing grid right over your desktop, so you can use it everywhere, with any drawing application without any special plugins for different graphic editors. More » |
All the contacts and projectsDmitry Vasiliev (just.dmitry)
Related LinksSoftware for Visual Studio .NET developers Software for Delphi and C++ Builder developers Software for Visual Basic 6 developers Delphi Tips&Tricks MegaDetailed.NET More Online Helps Win32 Programmer's Reference Win32 Multimedia Programmer's Reference OLE Programmer's Reference Microsoft Windows Pen API Programmer's Reference Microsoft Windows Sockets 2 Reference Microsoft Windows Telephony API (TAPI) Programmer's Reference Unix Manual Pages
|