About Revenera_Ian

Revenera_Ian · ‎Jun 22, 2021

Hi Srinivas (@srinivask), Thank you for your post. Are you referring to Interop.ISWiAuto26.dll, specifically with the Interop prefix? Also, is it correct to infer that you are using Visual Studio? The corresponding DLL for InstallShield 2020 is ISWiAutomation26.dll which is in your <IS_2020_HOME>\System folder where you installed your copy of the InstallShield 2020. If you are using Visual Studio, in your solution, you could try updating the current project reference to from ISWiAutomationXX.dll to ISWiAutomation26.dll for InstallShield 2020. Then build the solution. Is an Interop.ISWiAuto26.dll file generated in the project output folder? Please give that a try. Does that work for you? Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Revenera_Ian · ‎Jun 22, 2021

Hi @eladef, Thank you for your reply. Could you please navigate to Get Support > Open New Case in the top menu then open a new support ticket to track this issue? This will allow us to best track this issue in order to best assist you. Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Revenera_Ian · ‎Jun 22, 2021

Hi @Azmaeus, Thank you for your post. You could try downloading the Docker image with a preinstalled copy of the Standalone Build via the documentation at this link: https://community.flexera.com/t5/InstallShield-Knowledge-Base/InstallShield-StandAlone-Build-with-Docker/ta-p/127060 Please give that a try. Does that work for you? Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Revenera_Ian · ‎Jun 22, 2021

Hi @RickFrank, Thank you for your post. Did you, perhaps, click the Build button, highlighted in red, under MSIX, instead of the Build button, highlighted in green, under Build, see attached screenshot? In your project, is Build Windows App Package, set to Yes, see attached screenshot? If you set Build Windows App Package to No then rebuild the project, does the issue still occur? Please give this change a try. Does that work for you? Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Revenera_Ian · ‎Jun 16, 2021

Hi @bolshed, Thank you for your post. Please accept our apologies for the delayed response. InstallShield 2014 has reached its end-of-life, so InstallShield 2014 is no longer supported. Could you please upgrade to a supported InstallShield version and open a support ticket to track this issue so that we can proceed? This will allow us to best track this issue in order to best assist you. InstallShield End-of-Life Policy documentation link with information about end-of-life versions and supported versions of InstallShield: https://docs.revenera.com/eol/installshield.htm Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Revenera_Ian · ‎Jun 16, 2021

Hi Naveen ( @naveen9396), Thank you for your post. You could try using the XML File Changes View or the Text File Changes View. XML File Changes View documentation link: https://docs.revenera.com/installshield26helplib/helplibrary/XMLFileChangesView.htm Text File Changes View documentation link: https://docs.revenera.com/installshield26helplib/helplibrary/TextFileChangesView.htm Please give both of those options a try to see which works best for you. Do either or both options work for you? Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Revenera_Ian · ‎Jun 11, 2021

Summary: This article discusses how to configure a PowerShell custom action that grants permissions to Administrators and no other users. Solution: 1. Configure a PowerShell custom action that calls the following PowerShell cmdlet: Invoke-Expression -Command:"icacls 'C:\Program Files\Permission' /inheritance:r /grant Administrators:F" 2. Set In-Script Execution to Immediate Execution. 3. Sequence the custom action in the Install Exec Sequence After InstallFinalize with the following Install Exec Condition: NOT REMOVE~="ALL" See the attached sample project for more details. In this case, the PowerShell custom action sets the permissions on INSTALLDIR. Additional Information: Click here for the official Microsoft documentation, an introduction to PowerShell. Click here for the official Microsoft documentation about the Invoke-Expression PowerShell cmdlet. Click here for the official Microsoft documentation about the icacls Windows command called by the PowerShell custom action.

Revenera_Ian · ‎Jun 11, 2021

Hi @udhayavardhanen, Thank you for the update. I'm happy to hear that the suggestions resolved this issue for you. You are very welcome; happy to help. Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Revenera_Ian · ‎Jun 11, 2021

Hi @ksams97, Thank you for the update. I'm happy to hear that this issue was resolved. I've accepted your reply as a solution to this issue. Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Revenera_Ian · ‎Jun 11, 2021

Hi @spothuri, Thank you for your reply. Sorry about the delayed response. As of this post, InstallShield 2020 was released a while back. Only if you have not yet evaluated InstallShield 2020, you can evaluate InstallShield 2020 and see if the upgrade of your projects to InstallShield 2020 works for you. We cannot guarantee that the upgrade will be seamless. There were a few InstallShield versions between InstallShield 2016 and InstallShield 2020, so you would need to test and see whether you experience any issues with the upgrade. There are migration / upgrade scenarios where starting the project from scratch is best, but we will not know until you give the upgrade a try. Please give the upgrade a try. Does that work for you? Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Revenera_Ian · ‎Jun 11, 2021

Hi @ksams97, Thank you for your reply. Sorry about the delayed response. Could you please navigate to Get Support > Open New Case in the top menu and open a new case for tracking this issue in order to proceed? This will allow us to best track this issue in order to best assist you. Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Revenera_Ian · ‎Jun 11, 2021

Hi @garrasco, Thank you for your reply. I understand that no file is transferred, but could you please give this possible workaround a try just in case? Save the text substitution manually as a custom string then call FeatureSetTarget every time with the text substitution. Please give that a try. Does that work for you? I understand that I'm not referring to the same exact scenario but we still need to see whether the workaround happens to still apply. If it is not possible for you to even try the workaround, please let us know. Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Revenera_Ian · ‎Jun 11, 2021

Hi Martina (@martina_roubal), Thank you for your post. I researched this issue, and I did not find functionality similar to release flags but specific to InstallScript projects. At the current time, it looks as though this functionality is only available with Basic MSI projects and InstallScript MSI projects. Could you please navigate to Get Support > Open New Case in the top menu and open a new case to track this issue if you would like to proceed with requesting to have this issue addressed? That will allow us to best track this issue in order to best assist you. Please let us know if you have any questions or concerns. Thank you for your patience and cooperation. Thank you very much, Ian

Revenera_Ian · ‎Jun 11, 2021

Hi @garrasco, Thank you for your reply. You could try this possible workaround: After FeatureSetTarget is called, the files are transferred to the expected directory, but it only saves the text substitution once, the first time. So you could try, as a possible workaround, saving the text substitution manually as a custom string then calling FeatureSetTarget every time with the text substitution. Please give that a try. Does that work for you? Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Revenera_Ian · ‎Jun 11, 2021

Thank you for your reply, @Superfreak3. To clarify, the possible issues are DLL preloading and binary planting. The behavior of the setup.exe copying itself to the temp location then running from there is intended behavior meant to address the possible issues of DLL preloading and binary planting. There is no workaround, since this is the intended behavior by design. Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.

Online Status	Offline
Date Last Visited	‎Jan 30, 2023 12:16 PM

Re: InstallShield 2020 Premier - ISWiAuto26.dll

Re: Multiple components + single component as key file

Re: InstallShield VC++ 2019 Prerequisite restart the machine after the prerequisite installation

Re: 32 Bit legacy drivers

Re: Few newbie questions

Re: How to add Machine key to web.config file thru Installshield

How To Configure a PowerShell Custom Action that Grants Permissions to Administrators and No Other U...

Re: How to create installer for Web API using installshield

Re: Installation fails with error code 2343 (Specified path is empty) at the end of CreateFolders A...

Re: Issues while migrating from InstallShield 2016 to 2019 R2

Re: Installation fails with error code 2343 (Specified path is empty) at the end of CreateFolders A...

Re: FeatureSetTarget in Maintenance mode

Re: InstallScript project - release flags

Re: FeatureSetTarget in Maintenance mode

Re: Setup.exe Copying to Temp Directory on Launch... ?s

Re: Dynamic Link issue

Re: Xcopyfile does not copy empty folder

Re: Custom Action After Com Registration to run exe in [InstallDir]

Re: Custom Action After Com Registration to run exe in [InstallDir]

Re: CVE-2016-2542 in ISSetup.dll for Installshield 2020 and Installshield 2022

Re: InstallShield 2022

Re: Dynamic Link issue

Re: How To Build a Compressed Single EXE Installer

Re: The files of a specific component are not uninstalled during setup removal

Re: InstallSheld 2010 Express hangs, when "Extracting COM data from components"