I have a 64-bit MSI that I build with WiX. There is a bootstrapper that
launches the MSI. It passes a couple of parameters along to control the
install.
I'm finding, running on 64-bit Windows 7, that MSI is changing the value of
INSTALLLOCATION unexpectedly.
I explicitly pass in
"C:\Prog
Thanks, Phil. That's very helpful.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core appl
Sorry, I accidentally sent before done typing.
My google skills are failing me, and thought people here might be able to point
me in the right direction.
I'm charged with producing a new installer for a product using WiX.
The application architecture is that of a bare-bones shell that
1) re
I'm charged with producing a new installer for a product using WiX.
The application architecture is that of a bare-bones shell that
1) reads the name of a configuration file from the command line, then
2) reads in a list of .NET assemblies to load from the configuration file.
It's
---
I have an old out-of-process COM object that is wrapped in an EXE. It uses the
/regserver and /unregserver command line parameters to register and unregister
the COM object.
Heat appears to treat this as an ordinary executable, ignoring the fact that
it's a COM object.
Can Heat extract the C
eclarations, and add elements inside either
your element or one of your elements.
-Original Message-----
From: JK E-Lists [mailto:jkli...@ifm-services.com]
Sent: Wednesday, October 28, 2009 6:28 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How should I approach modularization?
I'm a total WiX noob, so please bear with me here. :)
I have a very large project that I'm writing an installer for. It has 2-3
scores of assemblies. The component list for the project is massive and
unwieldy. I want to break this up and group the component declarations
according to functionali
7 matches
Mail list logo