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: Create empty folders in Basic MSI
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 22, 2015
11:55 AM
Create empty folders in Basic MSI
Hello,
I am trying to create an empty folder on the C:\ drive, or wherever the main drive is, so on the Destination computer's folders feature, I tried using [WindowsVolume] and [PrimaryVolumePath] and created some folders there.
But nothing happens during installation, I can't find any of these folders being created.
Note: The program installs where I want it to, etc, except for these empty folders.
Thanks!
I am trying to create an empty folder on the C:\ drive, or wherever the main drive is, so on the Destination computer's folders feature, I tried using [WindowsVolume] and [PrimaryVolumePath] and created some folders there.
But nothing happens during installation, I can't find any of these folders being created.
Note: The program installs where I want it to, etc, except for these empty folders.
Thanks!
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 22, 2015
02:45 PM
Try creating a component with nothing in it and set the destination to the location and folder name that you want created
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 22, 2015
03:12 PM
Nope, it didn't work.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 23, 2015
07:28 AM
Create a Component with nothing in it and set the destination with the Empty folder you want to create ... say [INSTALLDIR]Dummy
make sure this component is associated to a Feature that's being installed.
make sure this component is associated to a Feature that's being installed.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 23, 2015
07:43 AM
Did you try basing your parent folder on the ROOTDRIVE property?
It's not visible in the project, but you can create an InstallScript CA to extract its value and set it to a Directory property.
*LE* also, did you check for permissions problems? (that's a bit of a long shot, because I presume you're running it as admin)
It's not visible in the project, but you can create an InstallScript CA to extract its value and set it to a Directory property.
*LE* also, did you check for permissions problems? (that's a bit of a long shot, because I presume you're running it as admin)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 26, 2015
09:35 AM
Yep, I'm running it as an admin.
I tried Creating a New Feature in Setup Design, and then adding a component with nothing in it. The Feature has the Destination [WindowsVolume]SOMENEWFOLDER
and also tried [PrimaryVolumePath]AFOLDER...
but still nothing happens. 😕
I'm running the Professional Version btw.
I tried Creating a New Feature in Setup Design, and then adding a component with nothing in it. The Feature has the Destination [WindowsVolume]SOMENEWFOLDER
and also tried [PrimaryVolumePath]AFOLDER...
but still nothing happens. 😕
I'm running the Professional Version btw.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 26, 2015
11:52 AM
Managed to get it to work, the feature wasn't installing. But now I have another problem...
Since I am using Basic MSI, and I have to install Feature A always. But Feature B ONLY if selected on the Custom Type Option
I have to go to Dialogs -> Setup Type -> Behavior -> Next -> Changed AddLocal to ALL. (Originally was Feature A that was the problem ). This kind of works.
If I try using the same but to Feature A only, and adding more items of AddLocal for EmptyFolderFeature it does not install. Any ideas?
Thanks!
Since I am using Basic MSI, and I have to install Feature A always. But Feature B ONLY if selected on the Custom Type Option
I have to go to Dialogs -> Setup Type -> Behavior -> Next -> Changed AddLocal to ALL. (Originally was Feature A that was the problem ). This kind of works.
If I try using the same but to Feature A only, and adding more items of AddLocal for EmptyFolderFeature it does not install. Any ideas?
Thanks!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 03, 2015
09:22 PM
I have a problem with this as well. Why won't installshield install empty directories???
My project is an installscript project. Certain components of our software expect certain empty folders to exist, in order for it to function correctly. So I have to somehow install/create them, and nothing is working. I have tried to:
1. Disable logging, and then use CreateDir functions, then Enable logging. This is only working in my service pack installers, not in the big installers, which span 5 DVDs. I can't figure out why, for the life of me.
2. Do as you said, and create empty components which install to the desired locations. This appeared to work as the installer was running (the directories were there). As soon as the installer finished, they were gone. The installer deleted them.
My project is an installscript project. Certain components of our software expect certain empty folders to exist, in order for it to function correctly. So I have to somehow install/create them, and nothing is working. I have tried to:
1. Disable logging, and then use CreateDir functions, then Enable logging. This is only working in my service pack installers, not in the big installers, which span 5 DVDs. I can't figure out why, for the life of me.
2. Do as you said, and create empty components which install to the desired locations. This appeared to work as the installer was running (the directories were there). As soon as the installer finished, they were gone. The installer deleted them.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)