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: Basic MSI Project - Adding files to components
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
Nov 16, 2009
08:42 AM
Basic MSI Project - Adding files to components
Im trying to produce a MSI of our current install, with this 1 component there is 2 folders in it but on the setup design you cannot add any additional folders....would i have to do this for every component that has more than 1 folder or is there an easier way?
Also is there a quick way to convert a Installscript project to MSI ?
regards,
Sniperkid
Also is there a quick way to convert a Installscript project to MSI ?
regards,
Sniperkid
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 16, 2009
11:32 AM
In a MSI project type each component only installs to one directory. This means that you will need to have at least one component per directory. Directories can be easier to manage in the Files and Folders view rather than the Setup Design view.
Unfortunately, there is no automatic conversion from an InstallScript project to a Basic MSI project. Probably the best thing to do is to start with a new Basic MSI project from scratch. Then you may be able to use some of your existing InstallScript code from within a custom action if you needed to do something custom that wasn't supported natively by MSI.
Regards,
Ajay
Unfortunately, there is no automatic conversion from an InstallScript project to a Basic MSI project. Probably the best thing to do is to start with a new Basic MSI project from scratch. Then you may be able to use some of your existing InstallScript code from within a custom action if you needed to do something custom that wasn't supported natively by MSI.
Regards,
Ajay