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
- :
- Re: Major Problems with String Resolvers in 11.5
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
‎Feb 17, 2006
06:26 PM
Major Problems with String Resolvers in 11.5
:mad: After upgrading our project to 11.5 from 11, we noticed that some of our registry entries were failing. These registry entries are using $P($P(beanId).key.version.major). Also failing is:
$P(beanId).key.UID) -> We are using this to check the VPD to see if our Windows service is already installed. Also using this to create a unique registry key for upgrade purposes, etc.
Additionally: As you probably know, the default installation path on Windows 64-bit systems is C:\Program Files (x86) for 32-bit applications. We're using the $PATH string resolver to remove any trailing slashes from our install path. With IS11.5, $PATH ends up being C:\Program Files(x86\CompanyName).
The Support team has confirmed both issues and entered work orders against them.
If anybody else has noticed similar problems in 11.5, please let me know.
Thanks,
Bruce
$P(beanId).key.UID) -> We are using this to check the VPD to see if our Windows service is already installed. Also using this to create a unique registry key for upgrade purposes, etc.
Additionally: As you probably know, the default installation path on Windows 64-bit systems is C:\Program Files (x86) for 32-bit applications. We're using the $PATH string resolver to remove any trailing slashes from our install path. With IS11.5, $PATH ends up being C:\Program Files(x86\CompanyName).
The Support team has confirmed both issues and entered work orders against them.
If anybody else has noticed similar problems in 11.5, please let me know.
Thanks,
Bruce
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 22, 2006
09:36 AM
Has this issue been resolved? I have a need for pre-install test to set a property value if the project/product has ever been installed. I cannot resolve $P($P(beanId).key.UID) from a custom event execute method.
Get "unable to find assembly with id" error
thx
Get "unable to find assembly with id" error
thx
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 22, 2006
10:43 AM
That's the error. As far as I know, there's no fix yet.
-Bruce
-Bruce
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 28, 2006
03:31 AM
Hi Bruce,
In connection to the following thread I would like to know if following issue is been resolved.
Even I am facing the same problem.
I am trying to get UID of the Feature and not of root Product.
I cannot resolve $P(beanId.key.UID) from a custom bean.
Getting "unable to find assembly with beanId" error.
Please let me know
Pradnya
In connection to the following thread I would like to know if following issue is been resolved.
Even I am facing the same problem.
I am trying to get UID of the Feature and not of root Product.
I cannot resolve $P(beanId.key.UID) from a custom bean.
Getting "unable to find assembly with beanId" error.
Please let me know
Pradnya
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 28, 2006
10:35 AM
Hi Pradnya,
Yes, this has been resolved in hotfix 11.5a.
Good Luck,
Bruce
Yes, this has been resolved in hotfix 11.5a.
Good Luck,
Bruce
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)