Am 23.02.2012 07:20, schrieb Rob Mensching:
> What are the exact error messages?
>
It depends. In VS2005/Votive I get the following messages. I have
removed the candle output though.
-- Rebuild All started: Project: NewSetup, Configuration: Debug x86
--
C:\Program Files (x86)
What are the exact error messages?
On Wed, Feb 22, 2012 at 9:47 AM, Andreas wrote:
> Hello,
>
> I have to author an installer that includes VC6 output and VS2005
> output. It needs the MSCOMMCTL and the VC80CRT. When I add both merge
> modules to the WiX project, I get the error ICE32.
>
> I hav
We solve this problem in Burn by caching the MSI locally.
On Wed, Feb 22, 2012 at 8:20 AM, Scharp, Craig
wrote:
> Hi wix users,
>
> Now that I have a setup.exe with a boot strapper to elevate my UAC, I'm
> finding a problem trying to make changes using Programs and Features after
> the product is
I am working on an installation sequencer. The heart of the sequencer is a
Windows system service that launches the install processes (typically
msiexec) as they come in.
The sequencer service is grabbing the environment block of the logged on
user (this has been verified) and passing this block t
Hello,
I have to author an installer that includes VC6 output and VS2005
output. It needs the MSCOMMCTL and the VC80CRT. When I add both merge
modules to the WiX project, I get the error ICE32.
I have downloaded the VS6SP6 merge modules here:
http://www.microsoft.com/download/en/details.aspx?di
Hi wix users,
Now that I have a setup.exe with a boot strapper to elevate my UAC, I'm finding
a problem trying to make changes using Programs and Features after the product
is installed. It asks for the MSI in temp folder, but since I used setup.exe
to install, it's not finding the msi. Does
Hi.
On Windows 7 64 bits version I have encountered a problem with our software.
I've used the MSCOMCT2.MSM for quite a number of years. It contains version
6.0.88.4 of the MSCOMCT2.OCX. At a customer pc with Win 7 64 bit, they have
installed a program which replace the OCX with a new version-
Thank you Peter. I will give this a try and let you know my results. I
appreciate the helpful and prompt feedback.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Wednesday, February 22, 2012 1:38 AM
To: General discussion for Windows Installer XML toolset.
Thanks for responding Rob. Forgive me if my terminology is off, I'm not
sure if it would be called a variable so let me show you and explain.
When I'm working in Visual Studio I would like to use a single name like
"SourceDir" instead of a relative path so that when the project is
published/built o
Look in the Wix help file under "Preprocessor". In the section called "System
Variables" there are some useful predefined values you can use.
$(sys.SOURCEFILEDIR) is the one you want.
-Original Message-
From: Troy Teixeira [mailto:tteixe...@polariswireless.com]
Sent: 21 February 2012 23:0
10 matches
Mail list logo