You may have luck changing what version of .NET you reference in Tools > Options. Referencing the 4.6 framework can result in a 1001 (fixed in late 2015 releases), and that could have changed outside of your project. ... View more

There are two things I would suggest. If this is just part of your tree, you could try putting p3 in a parent feature with A and B as its children. This will result in p3's feature being selected if A or B are selected. If instead this is the entirety of your feature tree, you could create a separate root-level hidden feature and put p3 in that. In either of those approaches, p3's presence will not affect A's and B's feature state, and you will avoid the indeterminate check box. ... View more

This is a known limitation. If you know what property or properties may change by a suite action, perhaps you can follow it up with one or more Set Property (UI) actions to trigger the update. ... View more

You can change the name of the folder that is used by editing the 'Package Files' node in the Packages view, so you can change the GUIDs to something "nicer". However we do not support removing that layer or using the same folder name for multiple packages, so you won't be able to put all the packages in a single folder. (Maybe we should expose the folder name as a setting on the package node...) (Actually I should check which version we added this to the IDE; before that you could get the same behavior by editing the .issuite file directly.) ... View more

It sounds like something may be off with the section in your project. You can ensure that InstallShield enables the necessary parents by listing them in the an appropriate child element of your project. See this related thread for some more details. ... View more

I would suggest using the iscmdbld.exe included in the trial of the IDE; we do not offer a separate trial of the Standalone Build. ... View more

You can use an Open action in your wizard, for example on the Finish button of your InstallationSuccess page. In InstallShield 2012 Spring I believe this looked like {Open PROPNAME} where PROPNAME can be substituted with the name of any property that contains the path to the exe you want to launch. Optionally you can specify some limited conditions by using more curly braces: {Open {PROPNAME},{OTHERPROP==VALUE}}. (The notation for this was heavily changed in InstallShield 2013, so the more recent documentation on this won't help you in InstallShield 2012 Spring or earlier.) ... View more

Yes. If you are referring specifically to the Standalone Build, I think there's even more flexibility as to what can be installed side-by-side than with IDEs. Unless you intend to use the automation interface, you can typically manage to install multiple of the same major version on the same machine. But that's not relevant to your question. ... View more

InstallShield 2010 and InstallShield 2015 are separate major versions, so yes. Both can be installed on the same machine. ... View more

If you specify a SHA1 certificate, InstallShield will generate a SHA1 signature. The most you should have to do is ignore (or disable) the warning. ... View more

Suite projects support several different package types, including .exe packages. But where possible, we suggest using a .msi package directly - for better progress reporting, transaction support, etc. - but in particular, try to avoid calling an .msi bootstrap .exe as an .exe package. ... View more

Ah, great workaround. I should have thought of that. 🙂 Note that you don't have to explicitly define the property for it to be empty, and in some ways using a crazy mix of letters in its name may help avoid it being accidentally overridden by an end user. That said, I'd probably go for something easy to understand, like [EmptyString]. ... View more

Yes, but this is not the approach that Microsoft recommends. Instead they seem to suggest that an application notify that it wasn't tested against a given version of Windows, but allow the installation to proceed. These days the reported version is largely controlled by the compatibility elements in the application manifest. InstallShield 2015 includes compatibility elements for Windows 10, so upgrading will address this for InstallScript projects. Note that Windows 10 shims Windows Installer custom actions, so InstallScript custom actions in an MSI project cannot detect Windows 10. ... View more

If you're merely looking to see if the key or value exists, prefer to use the Registry Exists condition. If you explicitly need to ensure that it exists and has a non-empty string for its value data, I think this may be a limitation in the current condition implementation. While the warning in the condition editor can be ignored, there's a run-time error if the Compare To value is empty. Is that run-time error what you're asking to address? In your ideal world, are you strictly looking for non-empty, or are there additional aspects to the value data that you would prefer to validate? ... View more

Microsoft does not grant redistribution rights on the debug merge modules. I believe you must get them from the machine that has Visual Studio, and are not allowed to share them beyond your local license. ... View more