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: Destination Folder needs to be partly hard coded
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
Jun 03, 2008
09:57 AM
Destination Folder needs to be partly hard coded
Project type - Basic MSI
What is the easiest way of controlling the user customisable directories? Basically what I want to be able to do is hard code the last bit of the directory structure: {user_selected_dir}\MY_FOLDER
I want to be able to graphically show this to the user and at the same time be able to do this in silent mode. (this wont be INSTALLDIR)
The only thing that I can think of is have 2 properties making up the destination folder - the first property for the users' selected dir and the second for the hardcoded bit. then make the component directories contain the 2 properties as their destination folder (is it possible to do this or will I have to create a custom action to do this?) I am trying to stay clear of custom actions. As good as they are they become a bit painful when the project gets bigger...
Am I approaching this the wrong way? Is there a smarter way of doing this?
What is the easiest way of controlling the user customisable directories? Basically what I want to be able to do is hard code the last bit of the directory structure: {user_selected_dir}\MY_FOLDER
I want to be able to graphically show this to the user and at the same time be able to do this in silent mode. (this wont be INSTALLDIR)
The only thing that I can think of is have 2 properties making up the destination folder - the first property for the users' selected dir and the second for the hardcoded bit. then make the component directories contain the 2 properties as their destination folder (is it possible to do this or will I have to create a custom action to do this?) I am trying to stay clear of custom actions. As good as they are they become a bit painful when the project gets bigger...
Am I approaching this the wrong way? Is there a smarter way of doing this?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 03, 2008
11:04 AM
Hmmmm, on second thought. Would it not be better to set the component path to [USER_SELECTED_DIR]\HardcodedDir and then on the Dialogs asking for the folder path have a caption that says something like "Please browse to the folder that contains "HardCodedDir"?
Would this be an acceptable solution?:confused:
This saves me messing around with CA that need to be called by the dialog's event and also to remember to call the CA in Exec sequences...
Would this be an acceptable solution?:confused:
This saves me messing around with CA that need to be called by the dialog's event and also to remember to call the CA in Exec sequences...
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)