About JayeshSoni

JayeshSoni · ‎Jan 17, 2023

It is working fine with your setup.exe. If I use " /S /v/qb+" with setup.exe it waits for the prq installation. Looks like issue is with the wrap.exe I'm using. I'll try to share that with you in some time or by EOD. Mean while can you tell me where can I check in that wrap.exe to resolve this error? as it was build using InstallShield only.

JayeshSoni · ‎Jan 17, 2023

Please see the attached screenshot. My point is when I use wrap.exe in PRQ, my main installer does not wait for the PRQ installation to complete. It just calls the wrap.exe and simultaneously the main installation begins. For better view added /S /v/qb+ in command under PRQ. you will see in screenshots what I'm trying to explain. IamgeStep1: Prompted for PRQ ImageStep2: PRQ installation was triggered ImageStep3: PRQ and main installation going side by side if I want I can even start with main installation without waiting for PRQ to complete.

JayeshSoni · ‎Jan 17, 2023

Thanks for the quick reply. I do have some OS Condition check added Yes the wrap is build using InstallShield. Which I am calling with /S /v/qn parameters. What I want is My main installation shouldn't start unless the PRQ is installed successfully. attached is the prq.

JayeshSoni · ‎Jan 16, 2023

I trying to run a wrap exe installer as a prerequisite which holds an MSI inside. When I launch my base installer(which is exe), It triggers the prerequisite for installation but doesn't wait for it. It proceeds with the main installation simultaneously. It only happens with warp exe, if I configure the same prerequisite directly with inbuild MSI it waits for installation to complete. Is there any additional settings or configuration I can make for exe Installer?

JayeshSoni · ‎Dec 15, 2022

I'm using IS 2020 R3 Professional Edition. Is there a way we can automate the patch process? Either by configuring a shortcut which points to a URL or by adding new services. If yes will like to know more about it, is it available in 2020 R3 Professional Edition? How can we configure it? Do we have any drawbacks?

JayeshSoni · ‎Jul 25, 2022

Hi All I have a doubt. For few of the component in a Installer I have " .NET Scan at Build" set to "Dependencies and Properties" and because of which at build time it identifies the dependent files and get it added to MSI. This components which are getting added at build time are having a unique name with all numbers and starting with "_" My question is, will this dependency components names will keep on changing every time I build the installer? Or there is a way to keep them constant as change in component name will give a problem in Small/Minor upgrade.

JayeshSoni · ‎Jul 06, 2022

Thanks for the reply Ian. So in this case the above scenario (the one I posted) is a not a minor upgrade? As I'm seeing configuration changes done successfully after installation and even IS_MinorUpgrade property is getting set in the log after the installation of 2nd Msi. Where for 2nd Msi, only 4th digit of product version and package code was revised.

JayeshSoni · ‎Jul 05, 2022

Hello, I have a small doubt regarding the MinorUpgrade. I know one way to cater that is by setting it up in Upgrade section. But what if I don't configure it will the below scenario still be a Minor Upgrade? Msi1 which is installed on Machine: Product Version 1.2.0.10 Msi2 having similar product code but different package code and version. Msi2 Product version 1.2.0.13 Will this still be a Minor upgrade? Note: After Msi2 installation, at the end of log after installation I can see configuration was done successfully.

JayeshSoni · ‎Jun 22, 2022

Thanks Varul, I'll try implementing this.

JayeshSoni · ‎Jun 22, 2022

Hi Varul Thank you for the quick reply. Also wanted to know about the un-installation behavior, I assume the feature will stay back because of this setting. How can we get this feature removed at time of uninstallation?

JayeshSoni · ‎Jun 21, 2022

Hello, I'm trying to install a particular feature only in Major upgrade mode. For which I have set the default " Install Level = 0" for that particular feature and added a condition as below. Condition: Level = 3, IS_MAJOR_UPGRADE but it is not working. Is there any workaround? Or am I missing anything.

Online Status	Offline
Date Last Visited	‎Feb 03, 2023 09:06 AM

Re: InstallShield pre-requisite for exe installer

Re: InstallShield pre-requisite for exe installer

Re: InstallShield pre-requisite for exe installer

InstallShield pre-requisite for exe installer

Auto Update minor changes

.NET Scan at Build setting for component.

Re: Minor Upgrade

Minor Upgrade

Re: Feature level condition

Re: Feature level condition

Feature level condition

Re: InstallShield pre-requisite for exe installer

Re: InstallShield pre-requisite for exe installer

Re: InstallShield pre-requisite for exe installer

InstallShield pre-requisite for exe installer

Auto Update minor changes

.NET Scan at Build setting for component.

Re: Minor Upgrade

Minor Upgrade

Re: Feature level condition

Re: Feature level condition