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
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
.® | 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
Our product has a requirement on SQL Server that must be tuned to our
application's requirements. I would like to create a bootstrapper to do the
following:
1. Bundle the most recent version of SQL Server Express into our
bootstrapper and install it, if SQL Server is not present.
2.
When a .NET package is successfully installed as a prerequisite for our Burn
bootstrapper application, and the user cancels the install, the bootstrapper
package is still listed in the Add/Remove programs. I understand that the .NET
package is part of the bundle but from a user's perspective
Phil: there's absolutely no need to apologise. All forum users (I know I am)
appreciate your input and time spent helping out on the forum.
I'll need to look into this issue anyway as part of a project of mine (which
I'll get back to soon I hope). I'll report back anything meaningful that I
We're doing a major upgrade and RemoveExistingProducts may not be schedule in
the most efficient place, i.e. between InstallValidate and InstallInitialize.
I'll attach the upgrade log in a following email as it's 42MB in size and I'm
not sure if it'll be allowed.
-Original Message-
We use a PowerShell script to upgrade our development servers and our product
is contained in a 1.7GB MSI file. The PowerShell script copies the package from
a network share to the local %TEMP% directory, then executes the MSI in silent
mode. Upon successful installation the copy of the MSI in
8 matches
Mail list logo
