This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- problem verifying installed products with registryService
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 04, 2007
02:44 PM
problem verifying installed products with registryService
Hello,
I'm having issues when trying to verify a product installation with the registryService. The code i'm using was working fine with ISMP 5.03, but no luck so far with ISMP 11.5 SP1 (myProduct is always null). The uid i'm looking up is for another ISMP 11.5 installation product, so i believe this should work.
Any known issues, troubleshooting tips?
Thanks,
Laurent.
WizardServices services = getProductBean().getServices();
RegistryService regserv = (RegistryService)services.getService(RegistryService.NAME);
myProduct = regserv.getNewestSoftwareObject(uid);
I'm having issues when trying to verify a product installation with the registryService. The code i'm using was working fine with ISMP 5.03, but no luck so far with ISMP 11.5 SP1 (myProduct is always null). The uid i'm looking up is for another ISMP 11.5 installation product, so i believe this should work.
Any known issues, troubleshooting tips?
Thanks,
Laurent.
WizardServices services = getProductBean().getServices();
RegistryService regserv = (RegistryService)services.getService(RegistryService.NAME);
myProduct = regserv.getNewestSoftwareObject(uid);
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 05, 2007
09:02 AM
a bit more details on this issue...
what i'm trying to do is to get information about the installation of product B when running the installer for product A.
With ISMP 5.03, I was able to do just that, but after some testing, it seems that with ISMP 11.5, the installer for product A can only gather information about installations of product A. Is this a known limitation/behavior?
what i'm trying to do is to get information about the installation of product B when running the installer for product A.
With ISMP 5.03, I was able to do just that, but after some testing, it seems that with ISMP 11.5, the installer for product A can only gather information about installations of product A. Is this a known limitation/behavior?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 05, 2007
09:22 AM
The format of the VPD registry changed with ISMP 10.5; perhaps look into the LegacyRegistryService interface to get information about an ISMP 5 installation from an ISMP 11.5 installation.
(Searching the docs for the word "legacy" should turn up other related information, such as the Legacy Uninstall action and the Legacy Install Location action.)
(Searching the docs for the word "legacy" should turn up other related information, such as the Legacy Uninstall action and the Legacy Install Location action.)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 05, 2007
09:40 AM
forgot to mention...
both products are installed with ISMP 11.5
both products are installed with ISMP 11.5
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 05, 2007
10:47 AM
One more question:
How do "manually" check that a product installation is indeed "registered" in the registry?
I'm wondering if the issue could be that the products i'm looking for are actually not properly registered in the registry (even though they are installed on the system...)
How do "manually" check that a product installation is indeed "registered" in the registry?
I'm wondering if the issue could be that the products i'm looking for are actually not properly registered in the registry (even though they are installed on the system...)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 05, 2007
11:04 AM
Please see the help topic "Location of the VPD Registry" for some information about where the VPD data are stored; I haven't looked at it for ages, but please also see "Using the VPD Exporter Utility" for information about a tool that might be of use.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 05, 2007
12:17 PM
alright, I finally figured this one out.
product A is set up with the default vpd location (under the installation information tab -> general information -> advanced properties), while product B was set up with a "custom" location.
Result is the registryService for product A is only looking at the vpd registry in the default location (or whatever location the project is set to) and will not look into the vpd registry of product B, since it is not in the same location...
So, to have my stuff working, i need to setup product A vpd location to be the same as product B.
It would be really nice if there was a way to set the vpd location on the registryService to accomodate that kind of issue. If product A has to look up for product B and C installation information, and product B and C are using different vpd location, there is no way to find that information at the moment.
Robert, how do make an enhancement request for this?
product A is set up with the default vpd location (under the installation information tab -> general information -> advanced properties), while product B was set up with a "custom" location.
Result is the registryService for product A is only looking at the vpd registry in the default location (or whatever location the project is set to) and will not look into the vpd registry of product B, since it is not in the same location...
So, to have my stuff working, i need to setup product A vpd location to be the same as product B.
It would be really nice if there was a way to set the vpd location on the registryService to accomodate that kind of issue. If product A has to look up for product B and C installation information, and product B and C are using different vpd location, there is no way to find that information at the moment.
Robert, how do make an enhancement request for this?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 08, 2007
06:35 PM
found this article describing how to query a VPD in a different location (exactly what I was looking for): http://support.installshield.com/kb/view.asp?articleid=Q112266
