Solution to MSI overwriting registry keys for another MSI
Hello,
I am looking at an issue where the two applications use crviewer.dll (one uses version 8.6 and one uses 8.5).
Script A points the below crystal registry keys to C:\Program Files\Seagate Software\Viewers\ActiveXViewer\crviewer.dll which is version 8.6.
Script B points the same crystal registry keys to C:\Program Files\app name\bin\crviewer.dll which is version 8.5.
HKEY_CLASSES_ROOT\TypeLib\{C4847593-972C-11D0-9567-00A0C9273C2A}\8.0\0\win32
HKEY_CLASSES_ROOT\CLSID\{13FA5947-561C-11D1-BE3F-00A0C95A6A5C}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{75347086-7260-11D1-BE46-00A0C95A6A5C}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{75C66E66-8949-11D2-BF6D-00A0C9DA4FA2}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{75C66E68-8949-11D2-BF6D-00A0C9DA4FA2}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{A0E5F37E-CA67-11D1-A817-00A0C92784CD}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{C4847596-972C-11D0-9567-00A0C9273C2A}\InprocServer32
What is the starndard process to prevent one application from overwriting registry keys used by another application?
Any suggestions on how this issue can be resolved long term – will application isolation correct this issue? If so, do I isolate both applications? I have never done any application isolation - is there any links/documents that can guide me?
Thanks in advance for any help.
Thanks,
Jason
I am looking at an issue where the two applications use crviewer.dll (one uses version 8.6 and one uses 8.5).
Script A points the below crystal registry keys to C:\Program Files\Seagate Software\Viewers\ActiveXViewer\crviewer.dll which is version 8.6.
Script B points the same crystal registry keys to C:\Program Files\app name\bin\crviewer.dll which is version 8.5.
HKEY_CLASSES_ROOT\TypeLib\{C4847593-972C-11D0-9567-00A0C9273C2A}\8.0\0\win32
HKEY_CLASSES_ROOT\CLSID\{13FA5947-561C-11D1-BE3F-00A0C95A6A5C}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{75347086-7260-11D1-BE46-00A0C95A6A5C}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{75C66E66-8949-11D2-BF6D-00A0C9DA4FA2}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{75C66E68-8949-11D2-BF6D-00A0C9DA4FA2}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{A0E5F37E-CA67-11D1-A817-00A0C92784CD}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{C4847596-972C-11D0-9567-00A0C9273C2A}\InprocServer32
What is the starndard process to prevent one application from overwriting registry keys used by another application?
Any suggestions on how this issue can be resolved long term – will application isolation correct this issue? If so, do I isolate both applications? I have never done any application isolation - is there any links/documents that can guide me?
Thanks in advance for any help.
Thanks,
Jason
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
MSIMaker
19 years ago
If you need to isolate the versions for each app then place the dll in the app folder and create .local files for the executables for that app. The app will then use the dll in te app folder before looking in the registry.
Your other option is to try to use the latest version dll and hope for backward compatability.
Your other option is to try to use the latest version dll and hope for backward compatability.
Posted by:
mickman
19 years ago
You can also try to use the same version (like 8.6) for both applications. Then you have to use the same Component ID's in bots msi's for the dll component.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
