Hello! Installshield has a limitation of 160 characters on the path length. We had a discussion with Flexera on this issue a couple of years ago, here is what they say: "When we build a release, we generally extract all the files during the build in the release location. And when all the files and folders are extracted, the path may get longer than the max length allowed by OS (256 charactes). Hence, I will recommend to have the release location as small as possible." "Our Engineering team confirmed that as per the documentation, recommended path length should not be longer than 160 characters, due to the limit by microsoft. In this case path length exceeding 160 characters,hence the behavior exists, as I mentioned previously try to reduce the path length below 160 characters to avoid the issue." Also, Flexera accepted our issue as an Enhancement request, but I guess that nothing has changed since then. BTW, we had to rename the mergemodules we use in order to satisfy the Installshield limits. ... View more

This had nothing to do with the Suite Setup! The Problem was produced by the msi-package, which afforded a restart (independently of the Service update). ... View more

The ProductVersion property is in fact that "ProductVersion" ... View more

If you want the parenting of the window to be correct, you have to use UI actions (including methods from ISuiteUIExtension) to show your message. These aren't currently available to PowerShell actions (or managed or InstallScript actions), so there is no parenting information, and then focus stealing prevention can cause the message box to be covered. ... View more

Right, gotcha. Hiding it doesn't work well if it's the parent of features you still want to show. ... View more

You may be able to get this with a custom validation action, but those currently have to be written in C++ or other native code, and that's only if the built-in cursor logic fits your needs. Other that that I'm out of ideas; we don't currently have a way to control the cursor position or put custom fields on a wizard page or secondary window. ... 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