one more remark about the your defined settings in the screenshots: if you have installed a version of Microsoft Visual C++ runtime 2015 and you have Microsoft Visual C++ runtime 2017 runtime as prerequisite, there will always be asked for a reboot. This because the VC 2015 runtime will be upgraded by the VCRuntime 2017. This means that the VCRuntime 2015 will be replaced by the VC Runtime 2017. If you have, like I do,  aswell the VC 2017 x86 as the VC 2017 x64 runtime included in your setup, your installer will ask 2 times for a reboot(after the x86 VC 2017 upgrade and after the x64 VC 2017 upgrade) when you use the option "Reboot the machine and resume on reboot" . This is maybe not the wanted behavior for your purpose. Take note of this. ... View more

@j_naed wrote: The newer versions can come from Microsoft products e.g. Visual Studio or Office. Not each minor version of the VC++ is distributed as a new redistributable. You have a point here... ... View more

Hi, I'm not with you in this. You say: 14.16.27029.1 is installed but 14.16.27027.1 is the newest available download??? From where does 14.16.27029.1 comes from when you can not download it (yet)?? ... View more

Watching yes, answering.... sometimes ... View more

I my opinion, I don't think this is possible. Or a single file setup or an msi, cab + setup.exe is the closest you get I suppose. ... View more

Janakiram wrote: Thank you Jenifer for the reply. Could you please help me with the steps how to do it? We have vc++ 2017 redistributes already downloaded. this is the PRQ i have created. Your check is wrong. Do not test for the uninstall key. This can return unwanted results. Microsoft releases sometimes a newer version of their 2017 runtimes and they use a different uninstall key. So you will not detect these. See this example of mine (Runtime 2015). Installshield does it also like this: ... View more

Patrick Simons wrote: Hello, I'm actually using InstallShield 2012 Spring Edition (Pro) and I'm planning to purchase InstallShield 2018. We're working with Basic MSI. Due to InstallShield Prerequisites we must deliver a Setup.exe Is it possible to compress the build, but to leave the MSI outside of the EXE-file? Regards, Patrick I get an msi, data1.cab(contains the to-be-installed files) en setup.exe(who contains the prerequisites). Is this something what you're looking for? ... View more

Anyone? What could be the reason for the error? And why is it pointing to the windows directory? ... View more

@DanGalender Then he still needs a script to set the correct productversion on buildtime 🙂 ... View more

Give some more info please! ... View more

So your application exists in your installer project out of different components. Lets say: comp A - version 1.2.0 com B - version 1.6.0 comp C - version 1.5.0 form application v1.8 so when you release application v3.0 with comp A - version 2.8.0 comp B - version 2.5.0 comp C - version 2.4.6 you can end up with application 3.0 with comp A V2, comp B V1 and comp C V2??? How do you test this as you have several different possibilities? Personally I think this is not a good approach. ... View more

You can write a script that modifies the productname in the ism (not the msi) BEFORE buildtime. Have a look at the ISWiProperty object of the automation interface. ... View more

haruka000 wrote: Does InstallShield 2015 Limited Edition work with window server 2016? I constructed an installer using Install Shield 2015 Limited Edition with Windows10 & Visual Studio 2015. I would like to know if this installer works in window server 2016. Thanks in advance! Why wouldn't it work? Are there any specific Windows 10 related things you do in your project? I would say, just give it a try and see if it fails somewhere. VMWARE is your friend ... View more

I'll give that a try. Thx! ... View more