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
- :
- directory structure wrong after install
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
Sep 17, 2010
02:09 PM
directory structure wrong after install
Project Type: InstallScript MSI
I've been playing around with trying to deploy our help files with a .msi installer (no Setup.exe). However, no matter what I do the directory structure is wrong after deployment. I have one component with two statically linked files and the rest are dynamically linked. The source structure looks like this:
When deployed, the directories are laid out:
Has anyone else seen this behavior before? When I use a Setup.exe the files are laid out just fine.
I'd like to launch this help installer as a Chained MSI but I can't do that if the MSI will be deploying the files incorrectly.
I've been playing around with trying to deploy our help files with a .msi installer (no Setup.exe). However, no matter what I do the directory structure is wrong after deployment. I have one component with two statically linked files and the rest are dynamically linked. The source structure looks like this:
Content/
Data/
Skins/
Show.aspx
Show.aspx.cs
When deployed, the directories are laid out:
Content/Data/Skins/
Show.aspx
Show.aspx.cs
Has anyone else seen this behavior before? When I use a Setup.exe the files are laid out just fine.
I'd like to launch this help installer as a Chained MSI but I can't do that if the MSI will be deploying the files incorrectly.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 20, 2010
01:46 PM
Am I the only one who has experienced this with a dynamic file link in a pure MSI package? Seems like a flaw in MSI or in the InstallShield interface. I can't fathom that every pure MSI package out there (created from InstallShield, of course) manually names each file in a component.