Is it possible to use Wix to programmatically create an MSI Installer using a
background process and an existing file structure? I would like to embed a
customized configuration file within their downloadable installation package.
I have never used Wix so any links to code or samples,
If your MSI packages are always the same apart from that single configuration
file, one way to do it would be to exclude file from the MSI. Then create a
single, static MSI and let the application download the config file at
runtime and configure itself, if it hasn't already done so.
This would
Unfortunately, based on our current requirements, we must not prompt the user
in any way nor may we require them to download a second file. Our client has
requested that certain customer-specific variables be known by the application
during install. The application must supply these variables
There are other ways you could do it but if you've been told how to implement
the requirement too, there's not much point going into it. To answer your
question...
Creating a process to make a Wix installer automatically is just the same as
making any automated build. If you use Votive (Wix
There appear to be 2 distinct problems here:
1) MSI's UI is not redisplayed on subsequent bootstrapper execution.
2) Install Conditions are not behaving as I expect.
I've discovered that the uninstall is happening because I have two msi
packages, one for 64-bit, and another for 32-bit. These
My guess would be because you are sharing UpgradeCode. When burn runs a second
time, the 32bit MsiPackage is going to detect based on upgrade code. Because
your InstallCondition evaluates to false, it schedules the removal of it.
-Original Message-
From: Karl Werner
Ah, that makes sense and may be what is causing the 32-bit msi to be
executed with uninstall. I'll look into how to fix that. Any ideas?
It does not however explain why the MSI's UI is never displayed . . . Even
if I take the InstallCondition out along with the second MsiPackage, I
still don't
So I populated the UpgradeCode using a pre-processor variable and use a
different code in the build properties for the x86 vs. x64 projects. This
seems to fix the uninstall issue.
Now back to how to re-display the MSI's UI on subsequent runs of the
bootstrapper?
Thanks!
Karl
On Tue, Jan 29,
While I'm still stuck on the core issue here of not being able to redisplay
the UI from the bootstrapper, I thought I'd document another way around the
ancillary uninstall issue:
Add a ComponentSearch for a component that the msi's will install:
util:ComponentSearch
But if the same component is used in both the 32 bit and 64 bit MSI, a repair
or removal is going to find InstallCondition=true for both packages.
-Original Message-
From: Karl Werner [mailto:karl.wer...@gmail.com]
Sent: Tuesday, January 29, 2013 11:12 AM
To: General discussion for
Since the bootstrapper isn't registering itself in ARP, that shouldn't
matter, right?
On Tue, Jan 29, 2013 at 11:24 AM, Hoover, Jacob
jacob.hoo...@greenheck.comwrote:
But if the same component is used in both the 32 bit and 64 bit MSI, a
repair or removal is going to find InstallCondition=true
But if they run the downloaded bundle a second time it would, I believe.
-Original Message-
From: Karl Werner [mailto:karl.wer...@gmail.com]
Sent: Tuesday, January 29, 2013 1:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Redisplay MSI's UI when
So if I use different upgrade codes, defined using pre-processor variables,
then that should prevent the problem in all cases, I suppose.
However, still stuck on the original problem - How can I get the MSI's UI
invoked on the second run of the bootstrapper.
On Tue, Jan 29, 2013 at 2:23 PM,
I'm creating a Bundle that installs the .NET Framework 4 and then SQL
Server Express as needed. The Chain element looks as follows:
Chain
PackageGroupRef Id=NetFx40Redist/
ExePackage InstallCommand=..
Id=SqlExpress2008x64
One of my partners was kind enough to post an Elance job to help entice someone
to demonstrate to how tackle my earlier question with WIX. The direct link
is...
https://www.elance.com/j/dynamic-wix-installation-package/37325289
Anyone interested?
-- G. Deward
Begin forwarded
I have installed my product and it works like a charm...
I have modified my install to work with Repair since I have a lot of custom
actions and 5 merge modules.
When I run repair all is good EXCEPT all files are being installed in 1
folder I have 5 folders:
C:\Program Files\MYCORP\MYCORP
On 29-Jan-13 16:10, Karl Werner wrote:
However, still stuck on the original problem - How can I get the MSI's UI
invoked on the second run of the bootstrapper.
You can't. Burn needs to know the operation being performed which it
can't if the operation is determined during the execution of the
On 25-Jan-13 10:44, Hoover, Jacob wrote:
I currently have a single MSI with ~30k components. During installations
and major upgrades it appears the sheer number of components is causing
performance issues (the files are data files so there aren't version info
headers). What is the best
On 28-Jan-13 16:24, John J. Hughes II wrote:
I have searched the web for Error 2896 which seems to say it is a UAC
problem but I also found references that say WixShellExec which prompt if
need for UAC permission so I would not expect that to be a problem but I am
new to the toolset.
On 29-Jan-13 17:39, Eric Schultz wrote:
If .Net Framework 4 is already installed, SQL Server installs fine. If .Net
Framework 4 is not installed, the SQL Server Express install fails because
it says the .Net Framework is not installed. In fact, it says it needs the
exact same version as was
I'm in a similar situation with close to 30,000 files to deploy of which
perhaps 50 - 100 are DLL's, EXE, OCX etc.
I've ended up grouping files together in a component, (with the exception of
DLL's etc) sometimes up to 5,000 or 6,000 in one component. I also forced a
version number for each
I think you'll find that SQL 2008 requires .NET 3.5 to be installed (SQL
2012 will work with .NET 3.5 or 4.0).
Neil
I'm creating a Bundle that installs the .NET Framework 4 and then SQL
Server Express as needed. The Chain element looks as follows:
Chain
PackageGroupRef
22 matches
Mail list logo
