Dmitry Streblechenko seems to indicate that his preferred method of
installing Redemption.dll is to have it self-register. However,
self-registering as a deployment method for dlls has fallen out of
favor.

I would like to create a Windows Installer correct merge module for the
custom Redemption dll that I'm about to make that my company will use.
I would like to get all of the registry values that Redemption creates
when it self-registers, and put those keys in the Registry table of my
merge module.

Will this work in all cases?

One concern I have is that Redemption.dll could have conditional code
in its implementation of DllRegisterServer such that the registry keys
it creates vary depending on the target system's setup. Can anyone
confirm or deny this?

Also, it would be most ideal if Dmitry would create a merge module for
his Redemption dll, so that users of it would have the one and only
correct merge module that they could then integrate into their
respective Windows Installer .msi packages. Are there any plans for
such a merge module?

Thanks!
Jeff