msix is relatively new to me and I don't know much about it yet.
But now I have the requirement to modify an existing msix package so that it is not installed to "C:\Program Files\WindowsApps\ ...". Instead it should install to "C:\Program files\..."...
May be someone had this case and can shed some light into the darkness.I have a windows installer package from another vendor and on some pc's when we try to install (via SCCM and also interactive) we get the error:System error 110. Verify that the ...
May be a stupid question, but is it the same for 32-Bit and 64-Bit OS ? Or should I call %systemroot%\syswow64\regsvr32 on 64-Bit OS because the DLL are 32-Bit ?regardsMarkus
Just tried with your attached prereq's and it worked in my InstallShield 2015.
May be the files are "blocked" because you received from the internet ?
regards
Markus
Okay,
I have attached a suite example with the check of the "Detected" state. In the suite I use two msi examples from the "InstallShield samples". But you can include also your own samples.
I also created a short film to demonstrate the use.
I hope ...
After the install of each package I check with a InstallScript function the "DetectedState" of the appropriate ParcelObject. The results are stored in a list. This allows me to analyze the results, etc.
svSuiteObjExpr = "[@Parcel(" + svPackagGuid + ...