And in the case of AD deployment, you'll just roll out a configuration file along with the MSI install?
-----Original Message----- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Friday, 3 October 2014 11:00 a.m. To: General discussion about the WiX toolset. Subject: Re: [WiX-users] What's the best way to deal with configuration data? I would only gather the minimum required information needed to install the application. Utilize a configure on first run model for application configuration, and write to an application/user defined storage location so that the user data is automatically persisted on repair/modify. Newer versions of Office do this from what I remember. -----Original Message----- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Thursday, October 02, 2014 3:46 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] What's the best way to deal with configuration data? That is correct. Information that needs to persist to a repair or upgrade is persisted in the registry. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -----Original Message----- From: Colin Sim [mailto:colin....@ipfx.com] Sent: Thursday, October 2, 2014 3:44 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] What's the best way to deal with configuration data? Hi guys, That sounds great and I've considered these approaches before. However, as I understand it (and I may well be wrong), when a repair or modify is invoked through the "Programs and Features" application (appwiz.cpl), it's not going to be able to see the original configuration file so all configuration properties are likely to use default values, which may be different to original setting. I suspect the registry is the most reliable storage location for these property values but again this doesn't seem like a good approach. Cheers, Colin -----Original Message----- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Friday, 3 October 2014 9:23 a.m. To: General discussion about the WiX toolset. Subject: Re: [WiX-users] What's the best way to deal with configuration data? I have an XML file driven approach where in it reads the XML file, sets the appropriate properties, and continues the install without further UI. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -----Original Message----- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Thursday, October 2, 2014 3:20 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] What's the best way to deal with configuration data? 2 is the approach I've been involved with, but the feature that makes it more corporate friendly is to allow it to be silent and read a file with all the parameters that would have been entered using the UI wizard. The general approach is that each relevant data item on a form has a public property associated with it (managed code here). Reflection can be used to set those properties. If each UI dialog was a form, then you can have a text file of data where each line is something like UserForm.UserName="Fred". That means set the UserName property on UserForm to Fred, and there'a public "Execute" method that's the equivalent of the Next button. The program itself knows that's invoked silently, so never invokes UI, it just does whatever it's told to do, setting properties etc. The UI is absolutely separated from doing the work so it can all be run from input data. It's the same general idea as silent MSI install with data passed as parameters. An extension would be to create a silent configuration file from a UI run as a model for all subsequent configurations or repairs of configuration. --------------- Phil Wilson On Wed, Oct 1, 2014 at 3:43 PM, Colin Sim <colin....@ipfx.com> wrote: > I have some questions about how best to deal with install or setup > configuration data. I apologies in advance if this is a repeat of something > that's already been covered in a previous post, but I haven't really found > anything that speaks to this subject. > > At my place of work we have three approaches to deploying various parts of > our system: > > 1. Install only: no configuration parameters in installer (i.e. no new > public MSI properties) and no setup application that is run after install. > > 2. Setup wizard: an application that is launched after installer to > guide a user through setting up a part of the application, e.g. setup a IIS > website. The advantage with this approach is that the installer is simple; > however, I do not believe this approach would scale or even work when > deploying through Active Directory. > > 3. Configuration in installer: common settings are built into the > installer, which then stores the values into the registry or configuration > files. Here are some reasons why I don't like this approach: > > a. When doing a repair or modify, a property may not be set to the > value of the original install; I know we could store the property value to > the registry and reload it there after for repairs, modify, and upgrade but > this feels like a rather messy approach. > > b. To work around some of the aforementioned issue, I'm seeing support > engineers editing the MSI property table to set property values, then giving > the installer to customers; hence, invaliding our digital signature. > > What I would like to know is if there are other approaches or if we're > largely putting them all in practice? Is there a best practice? > > Also, is it a good idea in general to just turn off the modify and repair > options? > > Cheers, > Colin > > This e-mail contains IPFX information which may be privileged or confidential > and is intended for use only by the individual(s) or entity named above. If > you are not the intended recipient, note that disclosing, copying, > distributing or using this information is prohibited. If you have received > this e-mail in error, please advise immediately to the e-mail address above > and permanently delete this message and any attachments. Please note that any > views or opinions presented in this email are solely those of the author and > do not necessarily represent those of the company. We monitor our e-mail > system and may record your e-mails. Thank you. > ---------------------------------------------------------------------- > -------- Meet PCI DSS 3.0 Compliance Requirements with EventLog > Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI > DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download > White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with > EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg. > clktrk _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
