Note If you are building a universal or mobile driver package, this directive is not valid. See Using a Universal INF File.
A RegisterDlls directive references one or more INF sections used to specify files that are OLE controls and require self-registration.
Each INF section referenced by a RegisterDlls directive must have the following entry format:
A register-dll-section can have any number of entries, each on a separate line.
Specifies the destination directory ID of the file to be registered. For more information, see Using Dirids.
If the control is not an executable file, this specifies the command-line argument to pass to the DllInstall function.
Each register-dll-section name must be unique to the INF file and must follow the general rules for defining section names. For more information about these rules, see General Syntax Rules for INF Files.
The following rules apply to the use of the RegisterDlls directive for device installations:
- Although the syntax permits filename to be either a DLL or an executable file, for device installations only a DLL is allowed.
- The code to be registered must not prompt for user input.
- Server-side installations execute in a system context. Therefore, you must be very sure that the code being registered contains no security vulnerabilities and that file permissions prevent the code from being maliciously modified.
For more information about OLE controls and self registration, see the Windows SDK documentation.
[Dialer] RegisterDlls = DialerRegSvr [DialerUninstall] UnregisterDlls = DialerRegSvr [DialerRegSvr] 11,,avtapi.dll, 1