We try to use IsCmdBld with our Installshield 2016 Express SP2 (on Win7 32bits) to make automation instead of manual building setup.exe
This is the command line : "C:\Program Files\InstallShield\2016\System\IsCmdBld.exe" -p "C:\test.ise" -y "2.10.15" -z "ProductCode={8EA39362-0CF1-4AE4-A14C-8F450FDE68BC}" -z "ProductName=Our product name including identity build number" ; product code is dynamically generated from SQL NEWID() each time.
Everything seems fine but we have strange behaviors :
- next time we compil our product, some component are not registred anymore (as if they unregistred theirselves) ; a "regsvr32" of these dll works until next IsCmdBld
- we have some error messages in some screens when we use old VB6 dlls ("Class not setup" for example)
If we made the build manually, everything is fine ... logs seems equal when manual or auto building ...
You mention that this occurs at compile time - therefore I'm assuming that you are using COM extract at build to extract the COM data from your files?
If you are building on a different machine to where Installshield is actually installed, make sure that these files have access to any dependencies that they would require to register successfully.
The error occurs at next compil because the dlls are unregistered after IsCmdBld has run previously ... but everything (VB, InstallShield) is on the same computer (VM actually)
