About dpothugunta5208

dpothugunta5208 · ‎Aug 18, 2018

$designerProject = New-Object -ComObject "ISWiAuto24.ISWiProject" $ismFilepath = "$scriptPath\Designer.ism" $designerProject.OpenProject($ismFilepath) I had no issues with the 2016. same code was working fine but after upgrading to 2018 getting the below error. (this is partial error list). New-Object : Retrieving the COM class factory for component with CLSID {520F427A-A0C0-48DA-B1D6-5AD84FEFD1A8} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). At D:\Murty Build Testing\ToolkitDesignerMSI\BuildToolkitOneDesingerMSI.ps1:78 char:24 + ... $designerProject = New-Object -ComObject "ISWiAuto24.ISWiProject" + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ResourceUnavailable: ( [New-Object], COMException + FullyQualifiedErrorId : NoCOMClassIdentified,Microsoft.PowerShell.Commands.NewObjectCommand

dpothugunta5208 · ‎Aug 18, 2018

Thank you so much. i implemented similar way.

dpothugunta5208 · ‎Aug 18, 2018

Hello MurtyIN, Did you got a solution. i am having the same error with the power shell. it was working fine up untill 2016. after upgrade i am getting the same error as yours. please let me know if you have a solution.

dpothugunta5208 · ‎Aug 02, 2018

We have just installed InstallShield 2018 Professional SP1 assuming we have the .NET 4.7.2. the max version i see is .net 4.7.1. How can i include this to our package and we need this as pre-req to our installation. Thanks in advance.

dpothugunta5208 · ‎Jul 25, 2018

Go to Application Data -> Files and Folders And on the 'Destination compute's files' middle pane, right click on the specific file and choose properties. you will get an option 'Always Overwrite'. Hope this helps.

dpothugunta5208 · ‎Aug 08, 2017

Hi, We have working MSI with no issues but wanted to find out how the add/remove program uninstall works. i dont see the uninstall string under the registery key - HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall and i dont see the uninstall.exe where we install the package i removed my MSI from the machine and if i go to my Add/Remove programs still i see the program un-installs successfully. Could you please help me where to look for the details how the uninstall working if i dong have the msi on my machine. Thanks.

dpothugunta5208 · ‎Apr 25, 2017

seandr wrote: I am attempting to create a single InstallShield project that I can use in combination with release flags to build a 32-bit or 62-bit version of my MSI installer. The installers are mostly same on the two platforms, the only difference being whether 32-bit or 64-bit versions of a couple of binaries are included in the MSI. Unfortunately, when I attempt to build the project with the 64-bit release flag, I get the following error: "ISDEV : error -5008: Intel64 or AMD64 must be specified in the template of the Summary Stream" because the Template Summary is set to "Intel". Is there a way I can conditionally change the Template Summary value to "x64" depending on the release flag value? Or can I dynamically change it based on a parameter passed to iscmdbuild.exe? Or some other way to programmatically adjust this setting? Did you found any solutions. i ham on the same boat. Looking if i can able to change this programatically?

dpothugunta5208 · ‎Apr 25, 2017

chad.petersen wrote: A package cannot be marked as supporting both 32-bit and 64-bit platforms. The Template Summary is a build time setting, not a runtime setting. You could build two MSI files, one 32-bit and one 64-bit and then wrap those in a Suite or Bootstrapper that determines the bitness and runs the appropriate one at runtime. That's a fairly common thing to do. Chad What if i leave Template Summary Empty. Can it work on any Target Machine bitness? what i read online if i leave empty then default would be 32 bit. but i need to make this value set dynamically. any other approach please?

dpothugunta5208 · ‎Apr 24, 2017

Hi, Currently we are using installscript to process the installation. we were using two separate 32 bit and 64 bit exe's. Now we would like to combine both 32 bit and 64 bit dll into one with differnt names. and based on the installed word document we will pick correct dll and install to the destination computer by programatically adding conditions to the InstalScript. My question is how to set the INSTALLDIR and Template Summary values dynamically. Thanks in advance for your help.

Online Status	Offline
Date Last Visited	‎Jun 30, 2020 01:35 PM

MSI & EXE projects InstallShelid automation using Powershell script failing in 2018

.net framework

Basic MSI project InstallShelid automation using Powershell script - error

.NET Framework 4.7.2

Re: Files won't overwrite

InstallShield 2016 - Uninstall

Re: Once IS project for 32-bit and 64-bit distributions

Re: Combining 32 bit and 64 bit dll

Combining 32 bit and 64 bit dll