InstallShield PRQ conditions don't seem to have the correct kinds of conditions to handle .Net Core installations.  Core is made up of several discrete runtimes that share common registry entries, so there is no way to tell which are present.  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET Core\Shared Framework\v7.0 is present if ANY of the 7.0.x runtimes are installed. dotnet --list-runtimes provides all the detail, but InstallShield's builtin PRQ conditions don't support interrogating this list.  Checking folder locations can't be used either because Microsoft included the sub-version in the path, like C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App\7.0.3.  When 7.0.3 is superseded by 7.0.4 or later the PRQ can't be stopped from running because only the specific 7.0.3 path is checked by the conditions. InstallShield needs new technology to enable these PRQs to be used correctly. ... View more

@alexcheng Good to hear you are able to solve the issue, thanks ... View more

Thank you, but that's not what I'm looking for.  Latest and Greatest may have been misleading.  I was hoping I'd be able to make my own, but I'm OK with asking for them here if that's an option.  I would like the latest versions of  .NET 5 Desktop Runtime,  the .NET Core Runtime 5, and the latest version of ASP.NET Core Runtime 5. ... View more

Hi,  Please download the attached prq for 5.0.13  x86 version and see it works or not for you ... View more

This error occurs During the installation process, a new plugin or theme creates a directory ( with the plugin or theme name) in the wp-content folder or you may encounter this error due to high memory usage and no disk space. Check out the following process to fix this error: 1. Create Backup 2. Disk Usage Optimization 3. Resetting File and Folder Permission 4. Setting File Permission via FTP Client 5. Monitor Application Logs I have gone through these steps using this guide: https://www.cloudways.com/blog/wordpress-installation-failed-could-not-create-directory/   Hope it will work for you. ... View more

Sorry Bikram,   I am very late in replying you as I was experimenting this and was also busy with other problems.   I could not accept your solution because of some observations - In case of a 64 bit machine with 64 bit OS and 64 bit office installed, and the application was using MS/Access developed using VS2010 and office 2010 - it required (after trial and error) the 32 bit Access database Engine of 2007. It was so strange. A prg can not make trial and decide which one will work. In case of a website - built with VS2019 on a 64 bit machine with 64 bit office professional 2019 with MS/Access, it required Access database engine of 2016 64 bit. Will get back to you further, if I get a solution. Studying on ACECORE.DLL - if including that in the application can solve the issue. Hope to hear observation of others in this regard. Thank you for your time and efforts. ... View more

I've already read those articles.  I noticed that the runonce key is generated once the user hits the "ok to restart" prompt.  Thus, I've tried putting a script to change the key on the on-rebooting event.  However, the documentation states that some actions may not be complete during on-rebooting because... the system is rebooting.  Yet, I can't find another event trigger that is safe to use.     ... View more

Hi Daejwitt, You can use "Custom" as Media type and 'Custom' as Disk Spanning options from Release Wizard.   Media type "Custom" can  work with multiple languages and multiple disks. Thanks ... View more

We had the same problem with adding the prq for .Net Framework 4.8 and used the prq supplied by Jenifer. The prq failed on one of our installs and tried to install the prq when 4.8 was already on the machine because the installed version was the ealier 528040 version. To fix this all that was needed was to change 528049  to 528040 because comparison 2 is 'Data on Target system is less than specified data'.  Therefore the line <condition Type="2" Comparison="2" Path="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" FileName="Release" ReturnValue="528049"/> is redundent as it is overwitten by <condition Type="2" Comparison="2" Path="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" FileName="Release" ReturnValue="528040"/>  Your conditions should only contain the one condition and look like this <conditions> <condition Type="2" Comparison="2" Path="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" FileName="Release" ReturnValue="528040"/> </conditions>   ... View more

I just saw you solution, after submitting a new Case for the same issue using InstallShield 2019, in my case I just had to delete the MVSN, .data and .001 files from c:\ProgramData\Flexnet.  I restarted Installshield and it is now activated.  Thanks for posting. ... View more

Hi @javasaran,   Again, you can use one more property to bind the string with your 'Text Area' control in Dialog. And the Property string can be changed from your custom action based on the virtualization value. Help net link for the Text are control:  https://helpnet.flexerasoftware.com/installshield25helplib/helplibrary/IHelpEUDialogsTextAreaProps.htm   Here, you can set the Text attribute of Text Area control to a property; Text = [VIRTULIZATIONSUPORT]  VIRTULIZATIONSUPORT is a property, its value can be changed based on the detection of virtualization. ... View more

Hi Ramesh P. I could see your case has been resolved from our side, we have returned your license. You need to use the same activation code that you used for activation earlier. Can you please check and confirm if that is working. Thanks, Bikram ... View more

Hi @ch_eng  Thanks for the info 🙂 Thanks, pgattu ... View more