t; From: doug.bod...@kantarmedia.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] LGHT0103 error where path is shorter than 255
> characters and file is present.
>
> I'm seeing a LGHT0103 error. The files are simply reported as not found;
> but they're there. If
13 15:47:35 -0300
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] LGHT0103 error where path is shorter than 255
> characters and file is present.
>
> 2013/8/23 John Ludlow :
> > One other question is what does D: map to? You mention network, which makes
> &g
2013/8/23 John Ludlow :
> One other question is what does D: map to? You mention network, which makes
> me wonder if this is a mapped drive. Does this work if you use an entirely
> local path? Some MSI operations cause errors if with mapped network drives
He said "Local disk, so transient network
August 23, 2013 16:56
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] LGHT0103 error where path is shorter than 255
> characters and file is present.
>
> You may already have verified this, but are you sure
> $(var.KMI.IntelliDrive
)KMI.IntelliDrive.ServicesHost.vshost.exe.config
?
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: Friday, August 23, 2013 16:56
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] LGHT0103 error where path is shorter than 255
characters and file is present
ugust 23, 2013 16:21
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] LGHT0103 error where path is shorter than 255 characters
and file is present.
I'm seeing a LGHT0103 error. The files are simply reported as not found;
but they're there. If you look at the light.exe command
I'm seeing a LGHT0103 error. The files are simply reported as not found;
but they're there. If you look at the light.exe command I ran below - I
grabbed the command text from a Visual Studio build log, and then ran
the ls command in powershell immediately after to demonstrate that the
file is there
I've been playing around with it some more and it seems that the problem is
tied to a poorly formed ExePackage block. After some discussions here it
doesn't make any sense for our deployment to use the RemotePayload option
since the software is to be deployed on isolated networks with no external
>From VS output window:
-- Build started: Project: VideoToolBootstrapper, Configuration: Debug
x86 --
C:\Program Files (x86)\WiX Toolset v3.6\bin\candle.exe -dDebug
-d"DevEnvDir=C:\Program Files (x86)\Microsoft Visual Studio
9.0\Common7\IDE\\" -dSolutionDir=C:\MissionManagement\VideoTool\C
Uhh, that is a really bad error message. What is the command-line you are
using to link?
On Wed, Jan 9, 2013 at 3:25 PM, Brad DuBois wrote:
> I apologize for the premature sending of the previous message.
>
> I'm currently riding the WiX learning curve and I have made some progress.
> I have m
I apologize for the premature sending of the previous message.
I'm currently riding the WiX learning curve and I have made some progress.
I have made a couple of .msi files that I have wrapped in a bootstrapper
application. The basic bootstrapper is working just fine so I am now
working on addin
I'm currently riding the WiX learning curve and I have made some progress.
I have made a couple of .msi files that I have wrapped in a bootstrapper
application. The basic bootstrapper is working just fine so I am now
working on adding on some prerequisite installations where I have ran into
this
12 matches
Mail list logo
