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
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.® |
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
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
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
On 01-Oct-14 18:43, Colin Sim wrote:
I have some questions about how best to deal with install or setup
configuration data.
Install defaults in per-machine locations (e.g., HKLM or ProgramData).
The first time the app runs, copy it to the running user's per-user
locations (HKCU/AppData).
--
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:
It depends. We don't access AD directly. We call ADFS through a wrapper
service. Since many of our services have hundreds of users, roles, etc., UI
entry is prohibitive. We load a database instead. Not as flexible, but plenty
fast.
--
John Merryweather Cooper
Senior Software Engineer |
Use Group Policy.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Colin Sim [mailto:colin@ipfx.com]
Sent: Thursday, October 2, 2014 3:20 PM
To: General discussion
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
10 matches
Mail list logo
