Any/all Powershell scripts are not working. Even a simple script (stored in Binary Table): trace-info -LogMessage “11111111I am a PowerShell custom action” $Value = get-property -name ProductName set-property -name NEWPROPERTY -value $Value All lines above are from Installshield's Help Library .NET 4.6.2 and .NET 4.7 are installed on two separate Windows 7 x64 (one hard; one vmware) The only message in the log file that seems out of place is: InstallShield: Couldn't resolve assembly by name System.Management.Automation.resources, Version=3.0.0.0, Culture=en-US, PublicKeyToken=31bf3856ad364e35 Any Ideas? ... View more

I am under the assumption that when using Text Files Changes and Insert at the beginning that the text that is inserted is followed by a line feed/carriage return. That does not seem to be the case. None of the actions text insertions are followed by a line feed/carriage return. Properties cannot contain a lf/cr so cannot use Properties (tried vbscript: Set Property("NEWLINE") = vbcrlf I can use String Editor to create a String with a lf/cr but cannot use Strings within Text File Changes Anybody know a way to add lf/cr to Text File Changes? Otherwise I will need to use some other method to edit the file ... View more

Looking for a Powershell equivalent to opening Database. With vbscrit I could simply edit a Database at runtime by using: Set View = Database.OpenView("SELECT * FROM `Registry` WHERE ` ") View.Execute Do Set oRecord = Nothing Set oRecord = View.Fetch If oRecord Is Nothing Then Exit Do ~~Retrieve row information View.Modify 6,oRecord 'delete ~~Enter new row information View.Modify 7,oRecord Loop View.Close Database.Commit This would edit the .msi at runtime if the condition in the registry table was found How to do this with Powershell? Cannot find too much info on using Powershell with Installshield or .msi's in general. ... View more

Have a Basic project that is near 2GB with over 18K files. No matter which OS I try to compile with I receive the following error: Windows 7 x64: Faulting application name: isdev.exe, version: 20.0.0.496, time stamp: 0x524bad45 Faulting module name: IsWiBuild.dll, version: 20.0.0.500, time stamp: 0x53972f73 Exception code: 0xc0000409 Fault offset: 0x000d1c58 Faulting process id: 0xcac Faulting application start time: 0x01d0bef579134887 Faulting application path: C:\Program Files (x86)\InstallShield\2013\System\isdev.exe Faulting module path: C:\Program Files (x86)\InstallShield\2013\System\IsWiBuild.dll Report Id: 0287cad1-2aeb-11e5-a353-005056c00008 Windows XP: EventType : BEX P1 : isdev.exe P2 : 20.0.0.496 P3 : 524bad45 P4 : IsWiBuild.dll P5 : 20.0.0.500 P6 : 53972f73 P7 : 000d1c58 P8 : c0000409 P9 : 0000000 I have yet to count the components in each Feature but would assume Installshield would show an error if too many Components. Any ideas? Going to try Command line build to see if it makes a difference. ... View more