Is there a fix available for this? For after all, this looks like a genuine bug in IsCmdBld as we've run automated signed builds for .ism projects for ages without problems, but a Suite project fails when signing SetupSuite64.exe.
Looks like signing takes place in the incorrect working directory, as I noticed that the SetupSuite64.exe file under the Redist folder in InstallShield installation directory is now signed by our certificate instead of Flexera's certificate. Shouldn't the file be copied to the build target folder first and then signed instead of trying to sign the original file that resides in a protected location?
