I guess this might be helpful First open your project in wordpad and search for product configuration section. Copy the whole section Open your second project in wordpad and paste the above copied configuration and rename the product configuration to some name and save it. Now open your second ism file with installshield IDE and youcan see the new configuration settings as well. ... View more

But the above solution is only applicable when the file is added individually to the component. If the file is in dynamic linking folder then how can we resolve this issue? ... View more

It appears the "-p" you posted uses a special character (an en dash?) instead of a hyphen; this often happens if you copied the command from Microsoft Outlook or Word. Same applies to the curly quotation marks around "patchexample", which want to be straight quotation marks. Perhaps type the command (instead of copying and pasting) and see what happens? ... View more

If I am not wrong you want to dispaly the feature according to the OS language. If yes it is very simple. Writeinstallscript function to get the locale info from th OS registry and store the result in some public property. Now in component condition ="GERMAN" "GERMAN" is the string which u need to assign to the property according to the language code getting from windows registry using by if else condition. In the above example if you give the condition like this whenever the property is set to german then only the component will be installed. Sequence this custom action in UI sequence as first action so that while installer initialisation the code will be executed and the components will be installed accordingly. ... View more

No ned to create any mergemodule to do this task. I guess you are using basic MSI project for your .Net project and your java project installer extn might be ans exe. If yes use custom action to execute the java exe in execute sequence whenever you want. For this you can use custom action readyly avalable in custiom actions type or you can implement your own logic through installscript and sequence it accordingly. Ex: See LaunchAppAndWait function for more details. ... View more

I guess your java project output file extn is .exe. If so you can use custom action to launch the exe file externally whenever you want to install your java installer. For this you can implement your own logic using installscript or use can use readymade custom action you can easily identify by custom action name itself. It might be helpful to you. ... View more

What type of project are you using? If it is basic MSI then you can export the dailog from that project and save as .isd file in your machine and import the same into your new project. ... View more

There is no actual method to export some features or components from one project to another project but we can try copy and paste I guess some times it wont help us I tried too. The second way is try open the both the project files(probably ism file or xml file) in notepad or wordpad and try to copy the required section from first project and paste into the second project. ... View more

Just check whether the build process is completing successfully before terminating ur batch or other script file. Or try to build manually through iscmdbld.exe in command prompt and observe. ... View more

I guess this forum is dedicated to installshield. ... View more

If you want to display the new dialog to the end user to take the input path to install second set of files into different directory then you need to cretae a custom dialog and sequence it according to your choice like before default installation dialog or after. or you can use the same default dialog adding browse button and textbox (same in the default dialog) which you can take inputs for both the target directories for this you need to set the public property(all in caps like MYOWNDIR) with the values of user selected directory paths. first one is : INSTALLDIR (by default) second one is our one: MYOWNDIR So now you can set the destination property value as MYOWNDIR to the component which you want to install second set of files. So that while installation it will resolve the property MYOWNDIR and it will install those files into appropriate folders. ... View more

You can maintain the same ism file for different releases. For minor upgrades we need to change the product version from 1.0 to 1.1 and then the installer will automatically treat the new installer as minor upgrade or release. For major upgrade we need to change the product version from 1.0 to 2.0 and product code as well. Any way package code will change automatically while building the installer everytime. I guess now you are very clear. If no please let me know your concerns. ... View more

I guess if we include the mst files in double codes the installer will take entire file as one string and it will try to execute the entire string Try like this "Transform1.mst";"Transform1.mst" ... View more

You can create a compressed installer it means all the files including msi file will be compressed in setup.exe. Once you double click on setup.exe it willcall the msi file intrenally and it will execute it. By doing sop go to IS2010->Releases->setup tab-> set setup type property to "Compressed" ... View more

Create a patch for your old installer including the files whichever you want to add files to your installe rmanually. Once you build and inatll the patch it will automatically install the new files without interrupting the old ones. I guess it might be helpful for you. ... View more