lkpevery.blogg.se - Are dll files dangerous

Security: The self registration process of a COM server may in certain cases perform unorthodox tasks such as modifying the system's network settings or perform other crazy maneuvers that have nothing to do with COM and are hard to identify and debug.

The rollback of COM data really does work like "auto-magic" tracking every change in the registry whether it be addition, modification or deletion and is reliable when done right. The result is that a failed setup may not clean up its COM footprint correctly and the MSI does not put the machine back in the original state properly.

Rollback: Windows Installer is unable to properly handle rollback unless the COM data is extracted and embedded in the MSI.

It is also possible to use the built-in SelfReg table in Windows installer to register the file using regsvr32.exe as part of the installation process (or even invoked as a custom action), but this is considered bad practice for a number of reasons: You can read more about these advanced MSI benefits in this summary that has become somewhat popular on : corporate benefits of MSI. This MSI SDK article lists several variations on the general issues with self registration described below, as well as describing some further details - particularly with regards to per-user registration of COM data, and run-from-source scenarios.Įxtracted COM data will ensure reliable installation of your COM server as well as support for advanced MSI features such as " advertisement", " rollback", resiliency and " elevated privileges".

Most MSI tools have features to support this COM extraction, see separate section towards the end of the answer for details.

The proper way to register a COM file is to extract the COM registry information from the file and add to the appropriate family of COM tables in the MSI. And one with WiX-focus: Registering COM EXE with WIX. Nice answer from Chris Painter, adding for reference: how to register DLL's properly in wix 3.9.