I have multiple COM dll projects and a setup project in one solution. The
setup project is referencing the outputs of the other projects and it is
configured to register the them using the 'vsdrpCOM' option.
Both build and installation on a clear machine run without errors, but one
of the COM dlls is not registered properly. This dll is compiled with the
MERGE_PROXYSTUB option and it registers interfaces. After installation, the
entries under HKEY_CLASSES_ROOT\Interface are missing. If I run regsvr32
after installation, the dll registers without problem and the application is
running.

So my question is: is the setup project intentionaly ignoring values under
HKEY_CLASSES_ROOT\Interface?

I also tried to change the registration method to self-reg, but then the
installation fails. This is also a potential bug, I guess. My dll depends
just on C and C++ runtime and I am using the WinSxS version of that. Maybe it
is not yet in place when the setup tries the self-reg action... That makes
the self-reg quite unusable.

Cheers