About regexmaster

regexmaster · ‎Mar 10, 2021

Our product writes a number of entries to the registry as DWORD values. I want to be able to preserve those through an upgrade. I've configured System Search to locate each these values (e.g. MyRegValueName) by name and store their data in a in a property (MYDATAPROP). I've then configured a component to install these values on condition of an upgrade. The registry for this component is configured such that in a key under HKCU a DWORD value for "MyRegValueName" will be configured with the data stored in [MYDATAPROP]. The problem is that "MYDATAPROP" stores integer "1" as string value "#1" and writes it to the registry as "#1", not "1". This means our product doesn't recognize it and cannot use it. What am I missing? I have failed to find a satisfactory answer in the forums. Any help much appreciated.

regexmaster · ‎Dec 03, 2020

Thank you for the suggestion. It is gratifying that through working on this it was becoming clear that leveraging path variables in our projects was the best way forward.

regexmaster · ‎Nov 30, 2020

We have recently migrated our source control system to Git and off of SVN. Our code developers love it, but SVN worked very nicely for staging and configuring sandboxes from which I built our installations. Thus far, git universe is proving to be a force fit for me, our installation developer. I have been looking for guidelines or suggestions from others who may have made this transition before who may be able to offer their expertise, or any pointers to a Best Practices document which might help me more intelligently configure my ISM project files for flexibility in our new environments.

regexmaster · ‎Aug 08, 2013

Very nice - Thanks! AmitRout wrote: Have a look http://blogs.flexerasoftware.com/installtalk/2011/01/building-32-bit-and-64-bit-installations-from-the-same-installshield-project.html

regexmaster · ‎Aug 07, 2013

I found this thread, which looks promising... Setting INSTALLDIR in Custom Action doesn't change install location

regexmaster · ‎Aug 07, 2013

I have exactly the same same situation and question, and am still looking for the solution. Any guidance would be very much appreciated. Many thanks

regexmaster · ‎Jul 17, 2013

Hi, All - Our MSI is orphaning two dll's and an exe file after the product gets uninstalled. I looked at the log file, and found these 4 files that certainly seem relevant to my problem, but I don't know what "blocked by the 1 mask argument" means, or why it's a problem. I tried searching the internets and the IS Community, but didn't find clarity. I will try adding entries to the RemoveFile table for the orphaned files, which I suspect will remove the orphaned files, but I would like to understand why I'm getting these log entries, and if there's a better way to make sure the files are removed on uninstall. Many thanks, dave MSI (s) (8C:58) [23:50:21:081]: WIN64DUALFOLDERS: Substitution in 'C:\Program Files (x86)\VantagePoint\Macros\Resource\comchartdir.dll' folder had been blocked by the 1 mask argument (the folder pair's iSwapAttrib member = 0). MSI (s) (8C:58) [23:50:21:081]: WIN64DUALFOLDERS: Substitution in 'C:\Program Files (x86)\VantagePoint\Macros\Resource\aspapi.dll' folder had been blocked by the 1 mask argument (the folder pair's iSwapAttrib member = 0). MSI (s) (8C:58) [23:50:21:082]: WIN64DUALFOLDERS: Substitution in 'C:\Program Files (x86)\VantagePoint\' folder had been blocked by the 1 mask argument (the folder pair's iSwapAttrib member = 0). MSI (s) (8C:58) [23:50:21:082]: WIN64DUALFOLDERS: Substitution in 'C:\Program Files (x86)\VantagePoint\VP.exe' folder had been blocked by the 1 mask argument (the folder pair's iSwapAttrib member = 0).

regexmaster · ‎Aug 26, 2011

Anyone figure out how to get this to work yet? Seems like it'd be wildly useful information.

regexmaster · ‎Oct 04, 2010

regexmaster wrote: I once tried to set permissions for the "POWER USERS" (or similarly named) group, and it worked on English OS's, but failed on Finnish, Spanish, Chinese, etc. The only workaround I could find at the time was to use the "Everyone" group because but it always felt a little too loose for what I really wanted. Well, I found out my problem with "Users" had to do with my "General" setting to use "Traditional Windows Installer Handling" by for setting permissions. To my embarrassment there's even a note in the InstallShield's IDE to the effect that many well known SID's aren't supported on non-English locales. Sorry for all my noise 😕

regexmaster · ‎Sep 30, 2010

slalande50 wrote: If you go to your component, click on the files item. Then right click on the files itself, you then click on the Permission button. Right click in the Names field and click on the New. Afterward remove the %USERDOMAIN and add USERS to the the user column. Then click on the Full Control item to give full control to all users. By the way, you can do the same for a folder by doing it in the "Files and Folders". Thank you for your answer. Would you happen to know if the "USERS" group exists for all OS Locales? (If not, I'll try it and post my results here.) I once tried to set permissions for the "POWER USERS" (or similarly named) group, and it worked on English OS's, but failed on Finnish, Spanish, Chinese, etc. The only workaround I could find at the time was to use the "Everyone" group because but it always felt a little too loose for what I really wanted. I've been hunting for exactly this kind of simple answer to this question and was lost in the sea of SID's and confounded by the documentation Microsoft's knowledge-base. (In fairness, the doc may have been very helpful and meaningful to someone who really knows about user account administration, but I am not he.)

regexmaster · ‎Oct 08, 2009

Thank you for the prompt reply. My read on this is, in short - My setup is fine, but the test is bad?

regexmaster · ‎Oct 08, 2009

I installed the SP1 update for IS2010, converted my earlier IS-2010 *.ism files, (0 errors/0 warnings). But now when I build my installations the Full MSI validation suite gives me a new error: ISDEV : error ICE27: Unknown action: 'MsiConfigureServices' of InstallExecuteSequence table. Not a standard action and not found in CustomAction or Dialog tables | InstallExecuteSequence | Action MsiConfigureServices. Any ideas on how resolve this ICE in a safe and efficient manner will be much appreciated.

regexmaster · ‎Aug 12, 2009

I got it, but I'm not thrilled with how I had to do it. I added a condition "Not IS_MINOR_UPGRADE" to the RemoveRegistryValues action, which happens to be fine in this case, since the upgrade doesn't need to remove any of the HKLM values.

regexmaster · ‎Aug 06, 2009

Are you able to create MSI logs, or do things not even get to the point where they would be useful? Does the patch work on some machines, but not others?

regexmaster · ‎Aug 06, 2009

The only post I could find related to this is here. Unfortunately, I still have not managed to successfully set this property for the case of a minor upgrade. if I try to set a msi command line item for the release to: REINSTALLMODE=voms then our setup runs in maintenance mode (to change or repair the previous installation) but no upgrade appears to have taken place. I must be missing something simple, and fundamental, but I'm all out of ideas.

Online Status	Offline
Date Last Visited	‎Mar 11, 2021 11:37 AM

Preserving DWORD registry values through an upgrade

Re: Guidelines for Configuring InstallShield projects to get installation content from Git repositor...

Guidelines for Configuring InstallShield projects to get installation content from Git repositories

Re: Single .ISM, multiple release targets; different INSTALLDIR targets, what's best way?

Found a helpful thread

Same question

Files Orphaned after our product is Uninstalled - Can't make sense of the Log

How about now?

"Users" group not available on all locales.

At last!

Thanks

Installed IS-2010 SP1; Converted project; Now Getting ICE27

Used a hack

MSI logs?

Setting REINSTALLMODE