Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL?

Christopher Painter wrote: Either way, I disagree with your `well supported story` theory as there is nothing in MSI or the SDK that discusses this story. That's like saying C doesn't support linked lists because the ISO standard doesn't document them. -- sig://boB http://joyofsetup.com/

Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL?

Christopher Painter wrote: I'm afraid you lost me there. Just about everything inside the MSI engine can be one outside of MSI. We were discussing simple property persistence. MSI has an equally simple declarative pattern: Write it to the registry during installation, read it back via

Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL?

I don't agree that installation and configuration are automatically distinct nor do I agree that configuration is generally per-user. In fact, 12 years of development, setup authoring and enterprise engineering has convinced me that it's generally per-machine. Even Windows Installer TAO seems

Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL?

[EMAIL PROTECTED] To: Bob Arnson [EMAIL PROTECTED] Cc: WiX Users wix-users@lists.sourceforge.net Sent: Monday, January 14, 2008 1:11:47 PM Subject: Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL? I don't agree that installation and configuration are automatically distinct nor

Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL?

@lists.sourceforge.net Sent: Monday, January 14, 2008 1:11:47 PM Subject: Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL? I don't agree that installation and configuration are automatically distinct nor do I agree that configuration is generally per-user. In fact, 12 years

Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL?

Richard wrote: Haven't you ever worked on a project where some enhancements are postponed in favor of working on More Important Things? More importantly, there's an easy pattern to do the same thing without custom actions. I'd rather the MSI team do the things in the engine that can't be

Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL?

I'm afraid you lost me there. Just about everything inside the MSI engine can be one outside of MSI. The reason I think this should be a built-in pattern of MSI isn't because I'm lazy or something, it's because I've spent a lot of time in the field working on this and I know it would be

Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL?

Christopher Painter wrote: I never understood why MSI doesn't have this automatic state saver pattern built in. Me either. Does anyone inside MS know why there isn't a mechanism to accomplish this? Regards Richard * C O N F I D E N T I A L I T Y N O T I C E *

Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL?

In article [EMAIL PROTECTED], [EMAIL PROTECTED] writes: Me either. Does anyone inside MS know why there isn't a mechanism to accomplish this? Haven't you ever worked on a project where some enhancements are postponed in favor of working on More Important Things? I tire of the endless

Re: [WiX-users] How do I preserve properties betweenINSTALL/UNINSTALL?

Tell me Rich, in a declarative programming language where custom actions are `evil` just who AM I supposed to complain to when I'm forced to color outside the lines for something that is obviously missing even after 9 years of production release? I don't buy `configuration data is a