Hi Team,
I have made one set up project Wix 3.7 version for our project
and it successfully creates *.MSI and installs the files in program files
folder as expected. Now we want to install one more MSI inside from our first
MSI.
While searching for it I found that this can be
No. Below is a General overview of how the Process Works:
1. Build a Setup for Project A.
2. Build a Setup for Project B.
3. Gather Prerequisites for Project A and B from Location C.
Now The Bootstrapper combines all those items into one unified setup,
and installs every item in a chain, i.e 1
No. This what Burn is for.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: dharma.t.gogin...@wellsfargo.com
See the other question I answered regarding the bootstrapper.
Carter
Quoting dharma.t.gogin...@wellsfargo.com:
I have 2 msi files one for my application and the other for sql
server native client. I have to install both at a time when a user
double clicks single msi?
Is there a way
*Tons of background...*
I have an MSI that installs three executables, a bunch of image files, and
a few INI files.
On the target device, which is similar to a cash register, two of the
executables (A1.exe and A2.exe) are always running, but the third
executable (N.exe) runs for about 10 seconds
I have 2 msi files one for my application and the other for sql server native
client. I have to install both at a time when a user double clicks single msi?
Is there a way where I can add an msi to the existing msi and have it such a
way that, when one msi gets installed, I can install the
I am new 2 wix.
I tried using burn but it is not generating the wixobj file. Below is the
bundle I am trying to create. Is there anything wrong in this. I already have
my two .msi's in sourcefile path. In the upgrade code I created a new GUID.
?xml version=1.0?
Wix
I have an exe that I'd like the MSI to execute as part of the installation
process. The exe does not need to remain on the system when installation is
complete.
This has to be a common thing to do. What is the common way to approach
this?
My original thought was to:
1) Copy the exe to
I don't have my packages on this system, so I can't look to see how I have
it working, but I believe you'd use a Binary / to reference the
executable, then a CustomAction with BinaryKey and ExeCommand
attributes to run it, and let Windows Installer take care of the temporary
nature of it.
Since
9 matches
Mail list logo