:: +=Description This is the type of client to be registered. +=Examples StartMenuInternet Mail Media IM JavaVM +=URL http://msdn2.microsoft.com/en-us/library/Aa390688.aspx http://msdn2.microsoft.com/en-us/library/aa969350.aspx +# :: +=Description The vendor must choose a canonical name for the program. The canonical name is never shown to the user, so it does not need to be localized. Its only purpose is to provide a unique string that can be used to identify the program. It is typically the same as the English name of the program, but this is merely a convention. For client types other than browsers, the canonical name can be any string. Choose a unique name, one that is not likely to be used by another vendor. For browser clients, the canonical name must be the name—including the extension—of the associated executable, for instance, Litview.exe. +=Examples Iexplore.exe Outlook Express Windows Media Player Windows Messenger +=URL http://msdn2.microsoft.com/en-us/library/Aa390688.aspx http://msdn2.microsoft.com/en-us/library/aa969350.aspx +# :: +=Description The LocalizedString value is a REG_SZ string and consists of an "at" sign (@), the full path to a .dll or .exe file, a comma, a minus sign, and a decimal integer. The decimal integer is the identifier (ID) of a string resource—contained within the .dll or .exe file—whose value is to be displayed to the user as the name of this client. Note that the file path does not require quotation marks, even if it contains spaces.Registering the displayed string in this manner allows the same registration to be used for multiple languages. Each language install provides a different ResourceDLL.dll file with the display name stored at the same resource ID. The LocalizedString and (Default) string values will both display the client's display name. If the LocalizedString is not present the (Default) value will be used instead. This works with all client types (Internet browsers, email browsers, instant messengers, and media players). +=Examples @FilePath,-StringID @C:\Program Files\LitwareInc\ResourceDLL.dll,-123 +=URL http://msdn2.microsoft.com/en-us/library/Aa390688.aspx http://msdn2.microsoft.com/en-us/library/aa969350.aspx +# :: +=Description A command line (shell) string which specifies a fully qualified absolute path to a file, followed by optional command-line options. Use quotation marks appropriately to ensure that spaces in the command line are not misinterpreted. The command line executes the program with appropriate defaults. Browsers generally default to the user's home page. E-mail programs generally open the user's Inbox. +=Examples "C:\Program Files\LitwareInc\Litview.exe" %programfiles%\Internet Explorer\iexplore.exe +=URL http://msdn2.microsoft.com/en-us/library/Aa390688.aspx http://msdn2.microsoft.com/en-us/library/aa969350.aspx +# :: +=Description A command line which specifies a fully qualified absolute path to the file, followed by optional command-line options. Use quotation marks appropriately to ensure that spaces in the command line are not misinterpreted. The reinstall command line declared in the ReinstallCommand value is executed when the user uses the Set Program Access and Defaults page to select your program as the default for its client type. The program launched by the reinstall command line should establish the program as the default for its client type. This can include operations such as registering file types and protocol handlers. Once the reinstall process is complete, the program launched by the reinstall command line should exit. It should not launch the corresponding program in interactive mode; it should merely register defaults. For example, the reinstall command for a browser should not open the user's home page. +=Examples "C:\Program Files\LitwareInc\Litview.exe" /reinstall "%programfiles%\Internet Explorer\iexplore.exe" –reinstall +=URL http://msdn2.microsoft.com/en-us/library/Aa390688.aspx http://msdn2.microsoft.com/en-us/library/aa969350.aspx +# :: +=Description A command line which specifies a fully qualified absolute path to the file, followed by optional command-line options. Use quotation marks appropriately to ensure that spaces in the command line are not misinterpreted. The command line declared in the ShowIconsCommand value is executed when the user checks the Enable access to this program box in the Set Program Access and Defaults page. This command line may restore your program's access points, including those in the Start menu, on the desktop, and in the Startup group, as well as normal automatic invocations, such as those specified in the Run registry key. +=Examples "C:\Program Files\LitwareInc\Litview.exe" /showicons "%programfiles%\Internet Explorer\iexplore.exe" -show +=URL http://msdn2.microsoft.com/en-us/library/Aa390688.aspx http://msdn2.microsoft.com/en-us/library/aa969350.aspx +# :: +=Description A command line which specifies a fully qualified absolute path to the file, followed by optional command-line options. Use quotation marks appropriately to ensure that spaces in the command line are not misinterpreted. The command line declared in the HideIconsCommand value is executed when the user clears the Enable access to this program box in the Set Program Access and Defaults page. This command line must hide all of your program's access points that are visible in the user interface. This includes access points in the Start menu, on the desktop, and in the Startup group. This command line must also prevent automatic invocations of the program, such as those specified in the Run registry key. You do not need to relinquish registration of file types when icons are hidden. +=Examples "C:\Program Files\LitwareInc\Litview.exe" /hideicons "%programfiles%\Internet Explorer\iexplore.exe" -hide +=URL http://msdn2.microsoft.com/en-us/library/aa969350.aspx http://msdn2.microsoft.com/en-us/library/Aa390688.aspx +# :: +=Description The icon resource takes the form of FilePath,IconIndex. The FilePath value is the full path to the file containing the icon. This path does not require quotation marks, even if it contains spaces. The IconIndex value is interpreted as follows: If IconIndex is a positive number, the number is used as the index of the zero-based array of icons stored in the file. For example, if IconIndex is 1, the second icon is loaded from the file. If IconIndex is a negative number, the absolute value of IconIndex is used as the resource identifier (rather than the index) for the icon. For example, if IconIndex is -3, the icon whose resource identifier is 3 is loaded from the file. +=Examples C:\Program Files\LitwareInc\Litview.exe,1 %programfiles%\Internet Explorer\iexplore.exe,0 +=URL http://msdn2.microsoft.com/en-us/library/Aa390688.aspx http://msdn2.microsoft.com/en-us/library/aa969350.aspx http://msdn2.microsoft.com/en-us/library/ms648050.aspx +# :: +=Description One of the pixels in an icon is designated as the hot spot, which is the point the system tracks and recognizes as the position of the icon. An icon's hot spot is typically the pixel located at the center of the icon. If you use the CreateIconIndirect function to create an icon, you can specify any pixel to be the hot spot. The icon resource takes the form of FilePath,IconIndex. The FilePath value is the full path to the file containing the icon. This path does not require quotation marks, even if it contains spaces. The IconIndex value is interpreted as follows: If IconIndex is a positive number, the number is used as the index of the zero-based array of icons stored in the file. For example, if IconIndex is 1, the second icon is loaded from the file. If IconIndex is a negative number, the absolute value of IconIndex is used as the resource identifier (rather than the index) for the icon. For example, if IconIndex is -3, the icon whose resource identifier is 3 is loaded from the file. +=Examples C:\Program Files\LitwareInc\Litview.exe,1 %programfiles%\Internet Explorer\iexplore.exe,0 +=URL http://msdn2.microsoft.com/en-us/library/Aa390688.aspx http://msdn2.microsoft.com/en-us/library/aa969350.aspx http://msdn2.microsoft.com/en-us/library/ms648050.aspx +# :: +=Description Assigning attributes to a file class allows you to control some aspects of its behavior. It also allows you to limit the extent to which the user can modify various aspects of the class, such as its icon or verbs, with the Folder Options property sheet. The attributes are defined as binary flags. To assign attributes to a file class, combine the selected attributes with a logical OR to form a single attribute value. Add an EditFlags REG_BINARY value to the class's ProgID key and set it to the attribute value. The following table lists the file class attributes and their numerical values. Flag Value Description FTA_Exclude 0x00000001 Exclude the file class. FTA_Show 0x00000002 Show file classes, such as folders, that aren't associated with a file name extension. FTA_HasExtension 0x00000004 The file class has a file name extension. FTA_NoEdit 0x00000008 The registry entries associated with this file class cannot be edited. New entries cannot be added and existing entries cannot be modified or deleted. FTA_NoRemove 0x00000010 The registry entries associated with this file class cannot be deleted. FTA_NoNewVerb 0x00000020 No new verbs can be added to the file class. FTA_NoEditVerb 0x00000040 Canonical verbs such as open and print cannot be modified or deleted. FTA_NoRemoveVerb 0x00000080 Canonical verbs such as open and print cannot be deleted. FTA_NoEditDesc 0x00000100 The description of the file class cannot be modified or deleted. FTA_NoEditIcon 0x00000200 The icon assigned to the file class cannot be modified or deleted. FTA_NoEditDflt 0x00000400 The default verb cannot be modified. FTA_NoEditVerbCmd 0x00000800 The commands associated with verbs cannot be modified. FTA_NoEditVerbExe 0x00001000 Verbs cannot be modified or deleted. FTA_NoDDE 0x00002000 The Dynamic Data Exchange (DDE)-related entries cannot be modified or deleted. FTA_NoEditMIME 0x00008000 The content-type and default-extension entries cannot be modified or deleted. FTA_OpenIsSafe 0x00010000 The file class's open verb can be safely invoked for downloaded files. Note that this flag may create a security risk, because downloaded files could contain malicious content. To reduce this risk, consider methods to scan downloaded files before opening. FTA_AlwaysUnsafe 0x00020000 Do not allow the Never ask me check box to be enabled. The user can override this attribute through the File Type dialog box. This flag also affects ShellExecute, download dialogs, and any application making use of the AssocIsDangerous function. FTA_AlwaysShowExt 0x00040000 Always show the file class's file name extension, even if the user has selected the Hide Extensions option. FTA_NoRecentDocs 0x00100000 Don't add members of this file class to the Recent Documents folder. +=Examples 30 00 00 00 02 00 00 00 +=URL http://msdn2.microsoft.com/en-us/library/Aa390688.aspx http://msdn2.microsoft.com/en-us/library/aa969350.aspx +# :: +=Description Handlers define the software portion of AutoPlay. They define the software's icon and friendly name, as well as the Component Object Model (COM) component to instantiate and how to initialize the component in response to an event. Each handler for a specific event registers as a value under the appropriate EventHandler key. When that event is detected, the user is prompted to choose a handler from a list of all the handlers registered for that event. Handlers and their associated values are defined under the AutoplayHandlers\Handlers key. Subkeys differ depending on whether the system can read device contents directly or whether the device provides contents to the system through a proprietary interface. +=Examples MSPlayCDAudioOnArrival MSShowPicturesOnArrival ... +=URL http://msdn2.microsoft.com/en-us/library/aa969331.aspx http://msdn2.microsoft.com/en-us/library/aa480152.aspx +# :: +=Description The Action value can be a literal value, for example "Play music", or a file name with a resource string. AutoPlay combines the Action value and the Provider value with the word "using" to create a friendly caption that displays in the user interface (UI). +=Examples Play Music @%SystemRoot%\system32\SHELL32.dll,-17156 +=URL http://msdn2.microsoft.com/en-us/library/aa969331.aspx http://msdn2.microsoft.com/en-us/library/aa480152.aspx +# :: +=Description The Provider value can be a literal value or a file name with a resource string. AutoPlay combines the Action value and the Provider value with the word "using" to create a friendly caption that displays in the user interface (UI). +=Examples Windows Media Player @%SystemRoot%\system32\SHELL32.dll,-17157 +=URL http://msdn2.microsoft.com/en-us/library/aa969331.aspx http://msdn2.microsoft.com/en-us/library/aa480152.aspx +# :: +=Description A CLSID is a globally unique identifier that identifies a COM class object. The HKEY_LOCAL_MACHINE\SOFTWARE\Classes key corresponds to the HKEY_CLASSES_ROOT key, which was retained for compatibility with earlier versions of COM. The CLSID key contains information used by the default COM handler to return information about a class when it is in the running state. To obtain a CLSID for your application, you can use the UUIDGEN.EXE found in the \TOOLs directory of the COM Toolkit, or use CoCreateGuid. The CLSID is a 128-bit number, spelled in hex, within a pair of braces. +=Examples {1FBA04EE-3024-11d2-8F1F-0000F87ABD16} {E0DD6CAB-2D10-11D2-8F1A-0000F87ABD16} ... +=URL http://msdn2.microsoft.com/en-us/library/ms691424.aspx +# :: +=Description A ProgID, or programmatic identifier, is a registry entry that can be associated with a CLSID. The format of a ProgID is .., separated by periods and with no spaces, as in Word.Document.6. Like the CLSID, the ProgID identifies a class but with less precision because it is not guaranteed to be globally unique. You can use a ProgID in programming situations where it is not possible to use a CLSID. ProgIDs should not appear in the user interface. ProgIDs are not guaranteed to be unique, so they can be used only where name collisions are manageable. The format of is .., separated by periods and with no spaces. The ProgID must comply with the following requirements: Have no more than 39 characters. Contain no punctuation (including underscores) except one or more periods. Not start with a digit. Be different from the class name of any OLE 1 application, including the OLE 1 version of the same application, if there is one. Because the ProgID should not appear in the user interface, you can obtain a displayable name by calling IOleObject::GetUserType. Also, see OleRegGetUserType The HKEY_LOCAL_MACHINE\SOFTWARE\Classes key corresponds to the HKEY_CLASSES_ROOT key, which was retained for compatibility with earlier versions of COM. +=Examples BDATuner.ATSCChannelTuneRequest.1 Microsoft.AnalysisServices.ActionInvocation.9 +=URL http://msdn2.microsoft.com/en-us/library/ms690196.aspx http://msdn2.microsoft.com/en-us/library/aa969374.aspx http://msdn2.microsoft.com/en-us/library/Aa767914.aspx +# :: +=Description The InitCmdLine value passes unaltered through the Initialize method before any other methods are called. IHWEventHandler::Initialize This method initializes an object that contains an implementation of the IHWEventHandler interface. Syntax HRESULT Initialize( LPCWSTR pszParams ); Parameters pszParams [in] Pointer to a string buffer that contains the string from the following registry value. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\AutoPlayHandlers\Handlers\HandlerName InitCmdLine= string Return Value Returns S_OK if successful, or an error value otherwise. Remarks This method receives the registry string stored in the InitCmdLine value under the AutoPlayHandlers\Handlers\HandlerName key. Applications that have registered with AutoPlay as event handlers place this string into the registry as part of the registration process. +=Examples PromptEachTime ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{640167b4-59b0-47a6-b335-a6b3c0695aea} "C:\Program Files\Movie Maker\moviemk.exe" /RECORD +=URL http://msdn2.microsoft.com/en-us/library/aa969331.aspx http://msdn2.microsoft.com/en-us/library/aa480152.aspx +# :: +=Description This is an event which is raised by a user’s action. +=Examples NeroAutoPlayVideoDVD MSCDBurningOnArrival +=URL http://msdn2.microsoft.com/en-us/library/aa969331.aspx http://msdn2.microsoft.com/en-us/library/aa480152.aspx +# :: +=Description Set this value to a friendly name for a feature, suitable to display to the user. This value can be either a REG_SZ or REG_EXPAND_SZ string, but it must be formatted as an indirect string (a fully qualified file name and resource value preceded by the @ symbol), for instance @%SystemRoot%\shell32.dll,-154. +=Examples @%SystemRoot%\shell32.dll,-154 @C:\WINDOWS\inf\unregmp2.exe,-9903 +=URL http://msdn2.microsoft.com/en-us/library/aa969374.aspx +# :: +=Description Set this value to a brief help message that the Shell displays for an object. The InfoTip displays as the contents of a mouse-over dialog box. This value can be either a REG_SZ or REG_EXPAND_SZ string but, like FriendlyTypeName, it must be formatted as an indirect string. +=Examples @%SystemRoot%\shell32.dll,-154 @%systemroot%\system32\ulib.dll,-1001 +=URL http://msdn2.microsoft.com/en-us/library/aa969374.aspx +# :: +=Description The part of a filename following the period in the full filename. +=Examples mp3 avifile (long extension) doc +=URL http://msdn2.microsoft.com/en-us/library/aa969370.aspx +# :: +=Description PerceivedTypes are similar to file types except they refer to broad categories of file format types, rather than specific file types. For example, Image, Text, Audio, and Compressed are PerceivedTypes. File types (generally public file types) can also have a PerceivedType, and should always be defined as such when appropriate. For example, the image file types .bmp, .png, .jpg and .gif are also of PerceivedType Image. The system defines several PerceivedTypes in Microsoft Windows XP. These include the following: * Image * Text * Audio * Video * Compressed * System +=Examples text image +=URL http://msdn2.microsoft.com/en-us/library/aa969373.aspx http://msdn2.microsoft.com/en-us/library/aa969371.aspx +# :: +=Description The purpose of MIME type detection, or data sniffing, is to determine the MIME type (also known as content type or media type) of downloaded content using information from the following four sources: * The server-supplied MIME type, if available * An examination of the actual contents associated with a downloaded URL * The file name associated with the downloaded content (assumed to be derived from the associated URL) * Registry settings (file extension/MIME type associations or registered applications) in effect during the download. In Microsoft Internet Explorer 4.0 and later, MIME type determination occurs in URL monikers through the FindMimeFromData method. Determining the MIME type allows URL monikers and other components to find and launch the correct object server or application to handle the associated content. This section provides a brief summary of the logic used in determining the MIME type from these sources, and also discusses some of the issues involved. +=Examples application/msaccess image/x-xbitmap +=URL http://msdn2.microsoft.com/en-us/library/ms775150.aspx http://msdn2.microsoft.com/en-us/library/ms775147.aspx +# :: +=Description The name of an application, specifically the application binary name. +=Examples Iexplore.exe Myapp.exe +=URL http://msdn2.microsoft.com/en-us/library/aa969373.aspx +# :: +=Description The fully-qualified path and file name. +=Examples %SystemRoot%\system32\NOTEPAD.EXE C:\myfile.txt +=URL http://msdn2.microsoft.com/en-us/library/aa969373.aspx http://msdn2.microsoft.com/en-us/library/aa969385.aspx +# :: +=Description A semicolon-separated list of directories. +=Examples C:\Program Files\Microsoft Office\OFFICE11\ C:\Program Files\Microsoft Office\OFFICE11\;C:\My\Custom\Path\ +=URL http://msdn2.microsoft.com/en-us/library/aa969373.aspx +# :: +=Description A text string describing a protocol. +=Examples http note +=URL http://msdn2.microsoft.com/en-us/library/Aa767914.aspx +# :: +=Description A command passed to DDEXEC. +=Examples Open("%1") [SetForeground][ShellNewDatabase "%1"] +=URL http://msdn2.microsoft.com/en-us/library/aa969321.aspx http://msdn2.microsoft.com/en-us/library/aa969384.aspx http://msdn2.microsoft.com/en-us/library/aa969385.aspx +# :: +=Description Strings stored in the registry do not switch language based on the user's UI language. For example, a Multilingual User Interface (MUI) version of Windows 2000 Professional is installed by first installing an English-language version, then adding the MUI Pack. When code loads a string from the registry, it will always get an English-language string, and hence the user will always see English for these strings in the Windows user interface. Obviously, this is not desirable. You might ask why you see German-language strings on a localized German-language Windows 2000 or Windows XP system. The answer is that the localized, German-language strings are stored in the registry as hard-coded strings. This is possible because the system is localized for a single language. In this design, single-language strings can be put into the Registry, just like English-language strings in the English-language version. This approach does not extend to an MUI system. All Windows Vista systems use MUI technology, even if only a single UI language is installed. The older model of localizing the operating system does not exist anymore. With Windows Vista, in the operating system itself, every language UI is running on top of a language-neutral base, with the corresponding UI resources for the language added in .mui files. The components of the Windows Vista operating system use the Registry in a language-neutral manner, following the same strategy described below. It is strongly recommended that multilingual applications running on Windows Vista follow this same approach. While it is technically possible to for an application developer to concoct a scheme to store string values in the registry for multiple UI languages, and to access the proper string at runtime, this is not recommended. Instead, overall system performance should be far better if applications follow the same approach as Windows Vista itself, introducing a level of indirection and letting the resource loader do the work of selecting the correct language resource. The remainder of this discussion assumes that your application is built with the Windows Vista SDK, that it is appropriately divided into an LN file and .mui files, that the .mui files are correctly installed as explained in Placement of .mui files, and that the application is intended to run only on Windows Vista or later. Given that, language-dependent strings stored in a string resource table can be made accessible via a language-neutral Registry value. The data for a language-neutral Registry value has the format "@,-[;]", where is the path of the Portable Executable, and is the numeric resource ID of the relevant string resource. The string itself is implemented just like any other localizable Win32 string resource. Note that the data for the Registry value makes no explicit reference to the .mui file: the correct .mui file will be determined at runtime, based on the current UI language preferences. The path may be specified with an environment variable, such as %ProgramFiles%, to support deployment. is optional. You can add it for debugging or readability of the value. The Registry APIs will ignore it when loading the string. Do not put a space between "," and "-" signs. (Correct example: "shell32.dll,-22912". Incorrect example: "shell32.dll, -22912".) A real-world example from within the Windows Vista operating system is a registry value with the data "@%SystemRoot%\system32\input.dll,-5020". Alternatively, the string reference can have the format "@,-", without path. An application that uses this approach must have some means (such as another Registry value) to communicate its own install folder. Code that reads these values from the Registry should load these strings by calling RegLoadMUIStringW. This API will load the string in the correct UI language. Your code won't need to deal explicitly with resource loading. Existing applications that are updating to this language-neutral use of the registry will typically want to keep their old string value (localized to English or to some other single language) in the Registry as a fallback and for backward compatibility. Furthermore, if a literal string is kept in the registry, and if a call to RegLoadMUIStringW fails, then the calling application can fall back to the literal string. (The authors of the application that consumes this information must decide whether and how to implement such a fallback; there is no special system support for this.) +=Examples @%ProgramFiles%\Windows AntiSpyware\MSASCui.exe,-208 @%ProgramFiles%\Windows AntiSpyware\MSASCui.exe,-104 +=URL http://msdn2.microsoft.com/en-us/library/ms904414.aspx http://msdn2.microsoft.com/en-us/library/ms776232.aspx +# :: +=Description When the user right-clicks an object, the shortcut menu contains all the normal verbs. However, there could be commands that you want to support but not have displayed on every shortcut menu. For example, you could have commands that are not commonly used or that are intended for experienced users. For this reason, you can also define one or more extended verbs. These verbs are also character strings and are similar to normal verbs. They are distinguished from normal verbs by the way they are registered. To have access to the commands associated with extended verbs, the user must right-click an object while pressing the SHIFT key. The extended verbs will then be displayed along with the normal verbs. +=Examples doit unzip +=URL http://msdn2.microsoft.com/en-us/library/aa969321.aspx http://msdn2.microsoft.com/en-us/library/aa969385.aspx http://msdn2.microsoft.com/en-us/library/aa969384.aspx +# :: +=Description A string of text. Set the value of MenuText to the text you want to be displayed in the Tools menu. This text does not support any underlining of characters for shortcut keys, because there is no way to prevent conflicts. For context menus, should be replaced with the text that you want displayed in the context menu. The name can include an ampersand (&) character, which will cause the character that follows to be underlined and used as a shortcut key. +=Examples Open Menu Close +=URL http://msdn2.microsoft.com/en-us/library/aa753591.aspx http://msdn2.microsoft.com/en-us/library/Aa753589.aspx http://msdn2.microsoft.com/en-us/library/aa753616.aspx +# :: +=Description A string of text. Set the value of MenuStatusBar to the text you want displayed in the status bar when the menu item is highlighted. This text should describe what the script associated with this menu item will do. +=Examples Working Done +=URL http://msdn2.microsoft.com/en-us/library/aa753591.aspx +# :: +=Description A string of text. Set the value of MenuCustomize to "help" to have the menu item appear in the Help menu. If this string value doesn't exist or is set to something other than "help", the menu item will appear in the Tools menu. +=Examples help NoHelp +=URL http://msdn2.microsoft.com/en-us/library/aa753591.aspx +# :: +=Description The path to a script to execute when the context menu is selected. +=Examples res://C:\Program Files\Adobe\Acrobat 7.0\Acrobat\AcroIEFavClient.dll/AcroIEAppend.html file://C:\myScript.js +=URL http://msdn2.microsoft.com/en-us/library/Aa753589.aspx http://msdn2.microsoft.com/en-us/library/aa753616.aspx +# :: +=Description Positions the menu item on the context menu. Set the value of Contexts to indicate which contexts your entry should appear in the standard context menu by using a bit mask consisting of the logical OR of the following values: Context Value Default 0x1 Images 0x2 Controls 0x4 Tables 0x8 Text selection 0x10 Anchor 0x20 For example, if you want your context menu entry to appear in the default context menu and when the context is a text selection, set the value of Contexts to 0x11. +=Examples 1 3 +=URL http://msdn2.microsoft.com/en-us/library/Aa753589.aspx http://msdn2.microsoft.com/en-us/library/aa753616.aspx +# :: +=Description Set the value of Flags to 0x1 to make the script run just as if it had been called through the showModalDialog method. Unlike the showModalDialog method, the script can access the window object of the parent window from the menuArguments property of the external object. +=Examples 1 +=URL http://msdn2.microsoft.com/en-us/library/Aa753589.aspx http://msdn2.microsoft.com/en-us/library/aa753616.aspx +# :: +=Description The name of the software vendor. +=Examples Contoso Microsoft +=URL http://no.url +# :: +=Description Internet Explorer uses two mechanisms for registering new URL protocol handlers. The first method is to register a URL protocol and its associated application so that all attempts to navigate to a URL using that protocol launch the application (for example, registering applications to handle mailto: or news: URLs). The second method uses the Asynchronous Pluggable Protocols API, which allows you to define new protocols by mapping the protocol scheme to a class. A URL follows the syntax described in RFC 1738, which specifies a protocol scheme followed by a scheme-specific portion (:). For example, in the URL http://www.microsoft.com/, "http" is the scheme and "//www.microsoft.com/" is the scheme-specific portion. The beginning section of the scheme-specific portion of the URL contains the server name. This portion of the URL is often referred to as the URL namespace. An asynchronous pluggable protocol handler is an apartment-threaded COM object that handles any calls made to the protocol scheme for which it is registered. When a client application makes a request, Urlmon looks up the protocol scheme in the registry and creates an instance of the protocol handler registered for that protocol scheme. If the protocol scheme was successfully mapped to the class identifier (CLSID) of a protocol handler, CoCreateInstance is called with that class asking for an IClassFactory interface. An instance of the protocol handler is obtained with IClassFactory::CreateInstance. +=Examples mime filter: application/vnd-backup-octet-stream x-microsoft-rpmsg-message webviewhtml protocol handler: http file gopher +=URL http://msdn2.microsoft.com/en-us/library/aa767916.aspx +# :: +=Description Asynchronous pluggable protocols offer three ways to map a protocol scheme to a class: Permanently registering an asynchronous pluggable protocol handler in the registry. The handler is used for any URLs with the specified scheme (such as HTTP, FTP, and so on). Temporarily registering a pluggable namespace handler. The handler is used for any URLs with a particular protocol scheme. This type is not handled in the tool. Permanently or temporarily registering a MIME filter. The handler manipulates the data stream it receives and returns a data stream for any resources of the specified MIME type. +=Examples Filter Handler +=URL http://msdn2.microsoft.com/en-us/library/aa767916.aspx +# :: +=Description A registry path to the location of an application's advertised capabalities. +=Examples Software\Clients\Windows Mail\Capabilities Software\Clients\Windows Media Center\Capabilities +=URL http://msdn2.microsoft.com/en-us/library/aa969375.aspx +# ::