Re: [WiX-users] Possible Bug: RegDelete does not work properly with REG_KEY_32BIT on a 64-bit system

by itself. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Edwin Castro [mailto:egca...@gmail.com] Sent: Thursday, July 16, 2015 8:18 AM To: General discussion about the WiX toolset. Subject: Re:

Re: [WiX-users] Possible Bug: RegDelete does not work properly with REG_KEY_32BIT on a 64-bit system

I can't use semi-custom-actions for this particular piece of work because I need to call an API to get permission to create, delete, or modify these particular registry keys. I work at a security company where they have implemented additional security features through drivers that disallow normal i

Re: [WiX-users] Possible Bug: RegDelete does not work properly with REG_KEY_32BIT on a 64-bit system

FYI - I just implemented a semi-custom action using a similar implementation as I found in the WixGamingExtension which calls WcaAddTempRecord on the Registry table, to allow MSI to manage my registry change. The CA code (specifically

Re: [WiX-users] Possible Bug: RegDelete does not work properly with REG_KEY_32BIT on a 64-bit system

You shuold OR it with the KEY_READ See Registry Key Security and Access Rights - Nir Bar Freelance Developer Mail: nir@panel-sw.com Web: www.panel-sw.com - C++ On Windows, Linux and Embedded Plat

Re: [WiX-users] Possible bug in 3.8

I've just started getting this "Failed to open the database..." error in the last couple of days. I'm still on WiX 3.7 and vs2010 (haven't even looked at 3.8 yet). I've changed *nothing* in my WiX projects or source. Thomas Due-3 wrote > Hello, > > I have tried the entire morning to register f

Re: [WiX-users] Possible bug in 3.8

Go here to get your activation email again: http://wixtoolset.org/issues/user The page that indicated the token expired should have had a link to get a new token. There was an issue with the mail server this morning being incredibly slow. -Original Message- From: Thomas Due [mailto:t...

Re: [WiX-users] Possible bug with WixUI_InstallDir?

http://wixtoolset.org/documentation/manual/v3/wixui/dialog_reference/wixui_installdir.html Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Re

Re: [WiX-users] Possible bug with Burn in perUser upgrade scenario?

com] > Sent: Friday, April 27, 2012 5:20 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Possible bug with Burn in perUser upgrade scenario? > > The wixstdba does not show special UI for upgrade scenarios. It just shows > install (or an error

Re: [WiX-users] Possible bug with Burn in perUser upgrade scenario?

The wixstdba does not show special UI for upgrade scenarios. It just shows install (or an error message if it thinks it will downgrade what is on the machine). That said, it should remove the previous Bundle when installing the new one. Can you share out more of the log? The part that shows the re

Re: [WiX-users] Possible bug in Lux

On 12-Jan-12 12:52, John Cooper wrote: > Bug is 3473007. Thanks; I'll take a look. -- sig://boB http://joyofsetup.com/ -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-

Re: [WiX-users] Possible bug in Lux

Bug is 3473007. -- John M. Cooper -Original Message- From: John Cooper Sent: Thursday, January 12, 2012 11:43 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Possible bug in Lux Sure. I'll get on it right after lunch. -- John M. C

Re: [WiX-users] Possible bug in Lux

Sure. I'll get on it right after lunch. -- John M. Cooper -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Thursday, January 12, 2012 8:39 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Possible bug in Lux On 10-Jan-12 17:48, John Cooper

Re: [WiX-users] Possible bug in Lux

On 10-Jan-12 17:48, John Cooper wrote: > Test NVPPTb.SetEditNetTcpBinding.Header failed with unknown operation. That's bad. But thanks for the repro! Can you file a bug on SF? -- sig://boB http://joyofsetup.com/ -- RSA

Re: [WiX-users] Possible bug in Lux

of NameValueSeparator values seems to work with multiple name/value pairs. -- John M. Cooper -Original Message- From: John Cooper Sent: Tuesday, January 10, 2012 11:27 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Possible bug in Lux Sorry for the dela

Re: [WiX-users] Possible bug in Lux

Henry & Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Saturday, December 31, 2011 10:40 AM To: wix-users@lists.sourceforge.net Subject: Re:

Re: [WiX-users] Possible bug in Lux

On 22-Dec-11 16:21, John Cooper wrote: > In partial answer to my own post, it appears that the Value attribute can be > formatted for Property Value Tests, but cannot be formatted for Multi-Value > Property Tests and Name-Value Pair Property Tests. Would be nice to allow > formatted values for

Re: [WiX-users] Possible bug in Lux

In partial answer to my own post, it appears that the Value attribute can be formatted for Property Value Tests, but cannot be formatted for Multi-Value Property Tests and Name-Value Pair Property Tests. Would be nice to allow formatted values for this attribute for all tests. -- John M. Cooper

Re: [WiX-users] Possible bug in WixUIExtension ?

On 25-May-11 18:12, DexterSinister wrote: > All I'm doing is adding a single dialog after CustomizeDlg ... and it works > fine during the initial installation, but when I try to use the 'Change' > option through Add/Remove Programs [in Win7 Pro SP1 32 or 64 bit], the > VerifyReadyDlg only has 'Back

Re: [WiX-users] Possible bug in Pyro

Ok thanks. -Original Message- From: Rob Mensching [mailto:rob.mensch...@microsoft.com] Sent: Wednesday, December 17, 2008 3:06 PM To: General discussion for Windows Installer XML toolset. Cc: Heath Stewart Subject: Re: [WiX-users] Possible bug in Pyro Heath needs to join the mailing

Re: [WiX-users] Possible bug in Pyro

To: General discussion for Windows Installer XML toolset. Cc: Heath Stewart Subject: Re: [WiX-users] Possible bug in Pyro Does anyone know if this is a bug or something I'm doing wrong? -Original Message- From: Rob Mensching [mailto:rob.mensch...@microsoft.com] Sent: Friday, Decemb

Re: [WiX-users] Possible bug in Pyro

Does anyone know if this is a bug or something I'm doing wrong? -Original Message- From: Rob Mensching [mailto:rob.mensch...@microsoft.com] Sent: Friday, December 12, 2008 2:44 PM To: General discussion for Windows Installer XML toolset. Cc: Heath Stewart Subject: Re: [WiX-users] Error 27

Re: [WiX-users] Possible bug, All of UI in Fragment included in MSI without UIRef

discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Possible bug, All of UI in Fragment included in MSI without UIRef Thanks for your response, interestingly enough, I was not using either a UIRef or a DialogRef to anything in the Fragment, expecting nothing would be included

Re: [WiX-users] Possible bug, All of UI in Fragment included in MSI without UIRef

Thanks for your response, interestingly enough, I was not using either a UIRef or a DialogRef to anything in the Fragment, expecting nothing would be included. Obviously that would not be the intended final result. I was referencing the dialogs in elements although, these elements were not in

Re: [WiX-users] Possible bug, All of UI in Fragment included in MSI without UIRef

The linker pulls in complete "sections". A Fragment creates one section. Thus, if you reference anything in a Fragment everything the Fragment is included in your output. If you want very granular inclusion of code, make appropriately small Fragments. -Original Message- From: [EMAIL

Re: [WiX-users] Possible bug with ICE31

Thanks Bob. From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: 30 January 2008 15:46 To: Ryan O'Neill Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Possible bug with ICE31 Ryan O'Neill wrote: This can be worked around by swapping the style and the t

Re: [WiX-users] Possible bug with ICE31

Ryan O'Neill wrote: Height="16" Property="MyProp" Text="{48}{\TS_MS_Sans_Serif_9}" TabSkip="no" Sunken="yes" /> This can be worked around by swapping the style and the text length delimiter around. The MSI still works as expected but the warning goes away. Height="16

Re: [WiX-users] possible bug

Adam Langley wrote: > The only registry entries are as following (*snip*) > That's the script generation phase. The script execution phase is where the values are actually written. Look for ActionStart(Name=WriteRegistryValues, ... to see the individual key/value writes. Make sure you genera

Re: [WiX-users] possible bug

[mailto:[EMAIL PROTECTED] Sent: Wednesday, 12 December 2007 5:43 p.m. To: Adam Langley Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] possible bug Adam Langley wrote: If I configure the File to place the dll in the GAC (vital/MSIL), because the file is no longer placed within the

Re: [WiX-users] possible bug

Adam Langley wrote: If I configure the File to place the dll in the GAC (vital/MSIL), because the file is no longer placed within the enclosing directory, the registry key is no longer created either. Should this really behave this way? Took me a while to find out what was going on, and