F
fiony
Guest
Hi, Gurus,
We have a set of COM components (DLLs) that are deployed as merge modules (*.msm) and shared by multiple applications. Recently we compile the source code to targeting x64 platform and build the 64bit merge modules.
After both the 32bit and 64bit merge modules are installed on Windows 7, the following KEYs can be found in register table:
HKEY_CLASSES_ROOT\MyComponent.ProgID
HKEY_CLASSES_ROOT\CLSID\{MyGUID}\InprocServer32 (64bit DLLs)
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{MyGUID}\InprocServer32 (32bit DLLs)
However, after the 32bit merge modules are uninstalled, the following KEYs are also removed
HKEY_CLASSES_ROOT\MyComponent.ProgID
How can I ensure that the ProgID keys under HKEY_CLASSES_ROOT will ONLY be removed after both the 32bit and 64bit merge modules are uninstalled?
Continue reading...
We have a set of COM components (DLLs) that are deployed as merge modules (*.msm) and shared by multiple applications. Recently we compile the source code to targeting x64 platform and build the 64bit merge modules.
After both the 32bit and 64bit merge modules are installed on Windows 7, the following KEYs can be found in register table:
HKEY_CLASSES_ROOT\MyComponent.ProgID
HKEY_CLASSES_ROOT\CLSID\{MyGUID}\InprocServer32 (64bit DLLs)
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{MyGUID}\InprocServer32 (32bit DLLs)
However, after the 32bit merge modules are uninstalled, the following KEYs are also removed
HKEY_CLASSES_ROOT\MyComponent.ProgID
How can I ensure that the ProgID keys under HKEY_CLASSES_ROOT will ONLY be removed after both the 32bit and 64bit merge modules are uninstalled?
Continue reading...