NET architecture, and a
bunch of other developer jargon (sorry). Suffice it to say, the majority of
these building blocks are registered in the HKEY_CLASSES_ROOT\CLSID
branch of your Registry, and are identified by a 32-digit (16-bit hex)
code called a Class ID, or CLSID. CLSIDs are formatted like this:
{AC0EEBCA-73FA-4EB3-87FF-96E58401FA1F}
Why is this important? It means that you can track down where a class
is referenced (in other words, where in Windows it??™s used) as well as
where it??™s registered, all by searching the Registry for the CLSID.
For instance, configuration data for the aforementioned class is located in:
HKEY_CLASSES_ROOT\CLSID\{AC0EEBCA-73FA-4EB3-87FF-96E58401FA1F}
If a component isn??™t working, odds are you can fix the problem, or at
least help diagnose it, by fussing with the values in this key. Or, delete
the key altogether to effectively unregister the class with Windows. For
instance, to turn off Vista??™s support for ???compressed folders??? (ZIP files
appearing as folders in Windows Explorer), you need to delete two such
CLSID branches, as described in Chapter 2.
Windows comes with a utility, regsvr32.exe, that you can
use to register or unregister DLL files manually. For instance,
you can repair a CLSID branch for a specific component by
opening a Command Prompt window (in administrator
mode; see Chapter 8) and typing regsvr32 "c:\program files\
my app\some file.dll" and pressing Enter. Or, to remove all
the entries used by a DLL, type regsvr32 /u "c:\program
files\my app\some file.
Pages:
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153