Thanks! That worked fine 🙂 ... View more

Thanks anyway. Shame that we have to tell people they need .NET Framework just for the installer but not the product itself now. Bit difficult to explain, but anyhow.  Our installers are so massive we don't have the time or money to rewrite them into something else so I guess we're stuck with this until we can move away from InstallShield completely. We're still on IS 2012 cause it hasn't really improved in 11 years and it wasn't very good in the first place, but it was good for it's time (20+ years ago). 😉 ... View more

you could try following codes, i think they will work. SetStatusWindow(30, "");   ... View more

Hi Mangus,  Since you you no longer have the old machine with InstallShield on it, you will need to contact Technical support using the contact information below. Technical support will help you return your InstallShield, and activate it on a new machine even if you do not have a valid maintenance plan.  Support contacts  https://community.flexera.com/t5/Support-Information/Support-Contacts/ta-p/94720 Please make sure that you have the activation code that you are using available if need to contact Technical support.  ... View more

I too was having the same issue. Remove ALL Com Extract at Build options from your com components. Do this under Installation Designer -> Components  for each component.  I make sure ALL components have this set to No.  Next, for every com component you are distributing you need to open the component (double click) and select files (personally I think it's good practice to have only ONE file for each component).  Right-click on the file and make sure Self Register is checked. But First: make sure the file does indeed need to be registered.  If you are redistributing controls from a third party not every file will need to be registered.  Unfortunately I haven't found a quick way to determine this so I run Regsrv32.exe on every file from an administrative command prompt.  If it needs to be registered you will get a success popup box.   If it doesn't need to be registered you will get an error about not finding an entry point.  That's cool, just ignore it and make sure you do not check Self Register. Note: I have had a couple of components that NEED to be registered not return either a success or error.  If that is the case then assume it needs to be registered and check Self Register. Note 2: if your components are 32 bit make sure you are testing with Regsvr32 from c:\windows\syswow64 instead of the one from c:\windows\system32.  The one in syswow64 is for 32 bit controls, the one in system32 is for 64 bit controls.     ... View more

@Magnus : Looks like this issue has been fixed in IS2018 release. IS2016, there were a limitation in number of character passed in command line parameter. Check IS 2018 release note  for more information : https://helpnet.flexerasoftware.com/installshield24helplib/rn/ReleaseNotes.htm#isreleasenotes_2630790174_1140855   IOJ-1823277 Calling a Basic MSI setup launcher from a command prompt and including parameters where the entire command exceeds 752 characters results in a “Setup Launcher Unicode Has Stopped Working” error. Although the error is seen, the MSI still launches and does contain all of the properties passed on the command line.     ... View more

Thanks, thats works fine! Regards Magnus ... View more

The Service Pack 1 really solved my problem, thanks! ... View more

Hi Magnus, I am not sure if your screen shot will work or not. Installshield uses not's to determine what OS are targeted. If you put a condition for w7 then the condition looks like not os1, not os2, not os3. I would suggest just removing any condition that specifies a user is using OS condition. Grant ... View more

Solution is found at: http://community.flexerasoftware.com/showthread.php?201770-Minor-upgrade-does-not-work&p=484914#post484914 ... View more

Try the following Take a copy of Installshield project source files that you used in last major release. Now paste all the changed files for minor upgrade on the location above. And use these files to create a minor upgrade. ... View more

When implementing this reattempt loop, the IsCmdBuild.exe successfully build in average on the 3:rd try. for (int i = 0; i < 15; i++) { if (RunCommandIsCmdBuild() == 0) break; } IsCmdBuild.exe => 0 if it has successfully build the installation. 20121001 094715: RunCommandIsCmdBuild(375): IsCmdBuild START attempt: 1 20121001 094715: RunCommandIsCmdBuild(377): WAIT 20121001 094716: RunCommandIsCmdBuild(379): IsCmdBuild STOP 20121001 094716: RunCommandIsCmdBuild(386): Got Error ExitCode: 1 20121001 094716: RunCommandIsCmdBuild(375): IsCmdBuild START attempt: 2 20121001 094716: RunCommandIsCmdBuild(377): WAIT 20121001 094717: RunCommandIsCmdBuild(379): IsCmdBuild STOP 20121001 094717: RunCommandIsCmdBuild(386): Got Error ExitCode: 1 20121001 094717: RunCommandIsCmdBuild(375): IsCmdBuild START attempt: 3 20121001 094718: RunCommandIsCmdBuild(377): WAIT 20121001 094725: RunCommandIsCmdBuild(379): IsCmdBuild STOP 20121001 094725: RunCommandIsCmdBuild(383): Got ExitCode: 0 ... View more

Yes, I removed the event in the SetupResume dialog and now the installation work like a charm, many thanks for all help I got from you!!! Regards Magnus ... View more

It's pretty well agreed in the WiX community that despite what the MSFT directions on MSDN say that a 1:1 file to component relationship with each file being a keyfile in it's own component is the default, general case to start with. There are times when you would steer away from this but this is the best way to start. The question I think the author is asking is how do you go about telling InstallShield that this is what you *WANT* when using the component wizards. I know I've asked in the past for a wizard configuration screen that allows you to define your component rules ( actually different profiles would be nice ) so that the authoring will be exactly the way you want when you do a big drag and drop. In my tool ( IsWiX ) I provide a simple radio selection that asks if you want one to many ( InstallShield / MSFT style ) or one to one ( WiX / MSFT style ) authoring for non-program executable files. ... View more