M
Marx
Hello,
Here's a scenario:
A component uses one version of Visio but the user may have two versions
installed.
e.g. Try to start Visio 2007 from the start menu when the previously started
version is Visio 2003 and Windows Installer starts with the following message
"Please wait while Windows configures Microsoft Office Visio <Edition>".
When the user tries to run an application that uses a Visio 2007 component
when the previously started version is Visio 2003 an error occurs.
Question:
What does Visio check for in the registry that kicks of the installer? It
will be nice to run this check and avoid the error.
The ConfigChangeID value at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Visio matches the most recently
configured one of
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Visio\Application or
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Visio\Application.
HKEY_CLASSES_ROOT\CLSID\{00021A14-0000-0000-C000-000000000046}\LocalServer32
holds the path of the most recently started Visio.exe but there does not seem
to be a valid cross-check.
I need to confirm the best practice for this scenario. Thanks for your help.
M.
Here's a scenario:
A component uses one version of Visio but the user may have two versions
installed.
e.g. Try to start Visio 2007 from the start menu when the previously started
version is Visio 2003 and Windows Installer starts with the following message
"Please wait while Windows configures Microsoft Office Visio <Edition>".
When the user tries to run an application that uses a Visio 2007 component
when the previously started version is Visio 2003 an error occurs.
Question:
What does Visio check for in the registry that kicks of the installer? It
will be nice to run this check and avoid the error.
The ConfigChangeID value at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Visio matches the most recently
configured one of
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Visio\Application or
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Visio\Application.
HKEY_CLASSES_ROOT\CLSID\{00021A14-0000-0000-C000-000000000046}\LocalServer32
holds the path of the most recently started Visio.exe but there does not seem
to be a valid cross-check.
I need to confirm the best practice for this scenario. Thanks for your help.
M.