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 setting Component's Destination property
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
‎Aug 28, 2007
09:15 PM
Problem setting Component's Destination property
I have a Basic MSI project and am having a problem setting a component's Destination property. I am trying to set it to a property I created in the Property Manager. When I type in the property, it says it's invalid.
So, what is the trick in doing this?
By the way, the property I created will hold a path that I am setting in a InstallScript Custom Action I wrote.
So, what is the trick in doing this?
By the way, the property I created will hold a path that I am setting in a InstallScript Custom Action I wrote.
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 28, 2007
09:40 PM
I believe the Destination wants to be a property from the Directory table; you can create one using the "Browse, create, or modify..." option under the component's Destination property.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 29, 2007
12:25 PM
I see what you're saying Robert.
Then, there is no way to create a property, and use the value of the property as the Component's Destination?
If that's correct, then I will have to figure out another way to do what I'm doing.
Then, there is no way to create a property, and use the value of the property as the Component's Destination?
If that's correct, then I will have to figure out another way to do what I'm doing.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 29, 2007
01:32 PM
Well, you could create a Directory property (DIR_THAT_I_WILL_CHANGE_LATER) with a dummy default value, use that as the component's destination, and then change the value from your set-a-directory or InstallScript custom action...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 29, 2007
03:42 PM
I tried that, but it does not seem to work. I am beginning to think that you can not use a user-defined property when you select a directory in the component's Destination property's "Browse for Directory" dialog box.
So, you define a new folder in the dialog, and use the property as the name of the folder, something like this, [USER_FOLDER], then say OK. The dialog will close and you are back to the Components view. So, click again on the Destination property, choose to Browse, the dialog comes back up, but this time when you look through the list of folders, you will see USER_FOLDER without the brackets. So, what happens is that it doesn't interpret this as a property, but rather as a string.
As a result, it doesn't worked like one would think. The component does not get added under the path of whatever the [USER_FOLDER] property is set to (of which I do through a custom action).
So, you define a new folder in the dialog, and use the property as the name of the folder, something like this, [USER_FOLDER], then say OK. The dialog will close and you are back to the Components view. So, click again on the Destination property, choose to Browse, the dialog comes back up, but this time when you look through the list of folders, you will see USER_FOLDER without the brackets. So, what happens is that it doesn't interpret this as a property, but rather as a string.
As a result, it doesn't worked like one would think. The component does not get added under the path of whatever the [USER_FOLDER] property is set to (of which I do through a custom action).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 30, 2007
09:38 AM
I'm not familiar with specific issues using custom component destinations; here's a recent thread doing kind of the same thing: [thread]172663[/thread]...