About Marc75

Marc75 · ‎Jan 06, 2016

Yes, package type is MSI. But I don't want to create my own prerequisite to avoid possible mistakes. Besides a prerequisite is available, but shipped with InstallShield 2015. Is there really no possibility to download the prerequisite that ships with InstallShield 2015? Also... the installlshield redistributable downloader, when you run this, you get a status message telling 'Last Updated 10/14/2008'?!?! What's the use of such a redistributable downloader? :confused:

Marc75 · ‎Jan 05, 2016

Hi, One month after purchasing InstallShield 2014, InstallShield 2015 was available which includes the Visual C++ 2015 Redistributable Packages. But how can I obtain the Visual C++ 2015 Redistributable Package without having to upgrade to InstallShield 2015? Thank you, Marc

Marc75 · ‎May 16, 2014

I have now created a custom action where I write each registry settings myself, but forcing it to the 64-bit portion. Not a great solution, but that works. Does anyone know a better solution for this? Thank you!

Marc75 · ‎May 15, 2014

Hi, I have a 32 bit installer package that installs 32-bit software. That software forces usage of the 64-bit key HKEY_LOCAL_MACHINE to read and write registry entries. My installer should prepare some registry entries that I configure during the user interface sequence. But the 32-bits installer should also write those entries in the 64-bit HKLM-part of the registry. How can I force the MSI WriteRegistryValues action to use the 64-bit registry part? I am able to write to the 64-bit registry myself, but all properties defined in the Registry Data views won't store themselves there. At the moment, I have tried to create custom actions just before the action WriteRegistryValues to force: Disable(WOW64FSREDIRECTION); REGDB_OPTIONS = REGDB_OPTIONS | REGDB_OPTION_WOW64_64KEY; But no luck yet. Thank you Marc

Marc75 · ‎Feb 02, 2012

Hi, it seems that the InstallShield documentation (2010) is not quite up-to-date. In the past there have been more issues with the patching mechanism: http://community.flexerasoftware.com/archive/index.php?t-107255.html The Windows Installer documentation now has another description listed for the function that is actually being called by InstallShield: MsiCreateTransformSummaryInfo http://msdn.microsoft.com/en-us/library/windows/desktop/aa370073(v=vs.85).aspx Please have the InstallShield documentation updated. And it would be great if the 'version relation' property would be pointed out in order to have the patches work the way someone want them to work. Perhaps updating an InstallShield White Paper would be great!! Thanks again for pointing me in the right direction! Marc

Marc75 · ‎Feb 01, 2012

Hi, First of all I'd like to thank you for helping me out. I've been struggling with this for over a year now and had this issue posted before without any replies! Your suggestion indeed helped me out! It now works the way I would want it to work. However, I do not understand these settings. I've probably noticed these settings in the past, but they are still confusing me! How can it be that (C) won't install over (A), but it does install over (B) when the option you mentioned is set to 'previous setup version = latest setup version'. For me it seems that it would only install if both versions were the same!? Would you please be so kind to clarify how I should read these possible settings? Thanks! Marc

Marc75 · ‎Jan 31, 2012

Hi, does anyone know how to create non-cumulative (minor upgrade) patches in InstallShield? When I create: - (A) baseline version 1.0 - (B) minor upgrade patch to 1.1 that targets 1.0 - (C) minor upgrade patch to 1.2 that targets 1.1 When I install the product (A) and then try to install the minor upgrade patch that should target 1.1 (C) it actually installs (!) leaving some files (available in (B) unpatched? I know I can create (C) to target (A) and (B), but I would like to create (C) to target (B), and (B) to target (A). I cannot find any documentation on this!? Any help would greatly be appreciated!! Thanks, Marc

Marc75 · ‎Aug 26, 2011

Randy, I'm taking your approach, but there is a function called PackageTitle() and used in the function RemoveOldCache(). It seems that it is yet another user function to retriece the package code? Would you be so kind to tell me how did you implement this? Thank you. Marc

Marc75 · ‎Aug 03, 2011

I would like InstallShield to inform the user which upgrade is taken place when a baseline version is already installed. Now it just says 'this setup will perform an upgrade'. Please extend this with version information like 'this setup will perform an upgrade of from to , at least for minor upgrades. thanks, Marc

Marc75 · ‎May 20, 2011

Hi Randy, thank you for the good explanation and for sharing the code with us! 🙂 Marc

Marc75 · ‎May 18, 2011

Hi Randy, you are right. It is dangerous if not done properly. Therefore, InstallShield should provide support for this feature in the first place. The simple cache clean script you are using, is it still the same as listed in the beginning of th thread? If not, would you please be so kind to share it with us? I really hope InstallShield will implement this in a future release. It will save a lot of work and a lot of disk space for anyone! 😛 Thanks! Marc

Marc75 · ‎May 18, 2011

Hi, why doesn't InstallShield support this feature out-of-the-box? They are the ones that give an option to locally cache the package, why don't they remove or at least give an option to remove these cached packages automatically? I've been using InstallShield for years now and I just stumbled across the cache location and found many locally cached packages for the same products! In my opinion the InstallShield product misses a big issue here! I'm guessing lots of setup administrators do not even know about this ....feature!It is even not mentioned anywhere in the InstallShield documentation. Hopefully InstallShield will add this 'delete cache'-feature in a future version! Where can I vote for it? :rolleyes: Marc

Online Status	Offline
Date Last Visited	‎Aug 31, 2020 11:44 AM

Re: How can I obtain Visual C++ 2015 Redistributable Package for InstallShield 2014?

How can I obtain Visual C++ 2015 Redistributable Package for InstallShield 2014?

work-around

how can I force writing regsitry entries into 64-bit part?

Re: need help with non-cumulative patching!

Re: need help with non-cumulative patching!

need help with non-cumulative patching!

Re: Local cached MSI does not get deleted when uninstalling

version update notification

Re: Local cached MSI does not get deleted when uninstalling

Re: Local cached MSI does not get deleted when uninstalling

Re: Local cached MSI does not get deleted when uninstalling

Re: How can I obtain Visual C++ 2015 Redistributable Package for InstallShield 2014?

How can I obtain Visual C++ 2015 Redistributable Package for InstallShield 2014?

work-around

how can I force writing regsitry entries into 64-bit part?

Re: need help with non-cumulative patching!

Re: need help with non-cumulative patching!

need help with non-cumulative patching!

Re: Local cached MSI does not get deleted when uninstalling

version update notification

Re: Local cached MSI does not get deleted when uninstalling