Redistributing ATL and OLE DB Templates
An Active Template Library (ATL) or OLE DB Templates project can be built for a MinDependency or a MinSize configuration.
A MinDependency configuration is what you get when you set the Use of ATL property to Static Link to ATL on the General property page and set the Runtime Library property to Multi-threaded (/MT) on the Code Generation property page (C/C++ folder).
A MinSize configuration is what you get when you set the Use of ATL property to Dynamic Link to ATL on the General property page, or set the Runtime Library property to Multi-threaded DLL (/MD) on the Code Generation property page (C/C++ folder).
MinSize makes the output file as small as possible but requires that ATL100.dll and Msvcr100.dll (if you selected the Multi-threaded DLL (/MD) option) are on the target computer. ATL100.dll should be registered on the target computer to ensure that all ATL functionality is present. ATL100.dll contains ANSI and Unicode exports.
If you build your ATL or OLE DB Templates project for a MinDependency target, you do not need to install and register ATL100.dll on the target computer, although you might get a larger program image.
If you redistribute an ATL executable application, you must register the .exe file (and any controls inside it) by issuing the following command:
where filename is the name of the executable file.
For OLE DB Templates applications, ensure that the target computer has the latest versions of Microsoft Data Access Components (MDAC) files. For more information, see Redistributing Database Support Files.
Installation of Localized ATL
If you use an ActiveX control that depends on Msstkprp.dll (typically they will be ATL-based controls) and you want to ship a localized version of the ActiveX control, you will need to ship a localized version of Msstkprp.dll. For more information, see article KB236404, "Microsoft Visual Basic 6.0 International Package and Deployment Kit," in the Microsoft Knowledge Base at http://support.microsoft.com.