Thanks a lot!
-Original Message-
From: ricky sundrani [mailto:rickysundr...@gmail.com]
Sent: Monday, January 18, 2010 9:03 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] FatalError
You can see the log to find out where the installation is failing.
U
You can see the log to find out where the installation is failing.
Use:
msiexec /i /l*r
On Mon, Jan 18, 2010 at 10:51 AM, C P wrote:
> Hi, my Installer is successfully compiled and can be successfully installed
> on few PCs, but on few PCs it shows FatalError dialog right after running.
>
Keep the user's group on the thread since others could learn/contribute.
The VSTO runtime uses "legacy" support in ARP (since they use a bootstrapper
that covers several MSIs under-the-covers), while most WiX-based installers
use the MSI support built into ARP.
From: nandini sa [mailto:nand
Hi, my Installer is successfully compiled and can be successfully installed
on few PCs, but on few PCs it shows FatalError dialog right after running.
How can I catch the reason of error?
--
Throughout its 18-year hi
Why does this wxs file work (i.e. the single file to install is installed at
the correct location)
http://schemas.microsoft.com/wix/2006/wi";>
but not this one?
http://schemas.microsoft.com/wix/2006/wi";>
Thanks for the responses. I'm not comfortable with giving the build service
account admin privileges. Maybe if the whole build thing was in a VM I
could do that. Something to look into.
--
Andrew Arnott
"I [may] not agree with what you have to say, but I'll defend to the death
your right to say
On 1/17/2010 11:10 AM, Giora keinan wrote:
> I have a problem in minor update. In minor upgrade the msiexec is
> looking for the upgrade name, which should be the same as the original
> msi name.
> The problem is that sometimes the original setup filename is modified
> during download. For example
On 1/15/2010 2:52 AM, Robert Barnes wrote:
> actually a part of my product! However this same dll is used by both
> my product and the other program - same dll, same name but installed
> into two different directories, so the other program is not actually
> using the dll that is being installed it
Hello
I have a problem in minor update. In minor upgrade the msiexec is
looking for the upgrade name, which should be the same as the original
msi name.
The problem is that sometimes the original setup filename is modified
during download. For example setup.msi is modified to setup(1).msi.
I r
9 matches
Mail list logo