[wix-users] how to debug/locate LGHT0001 error?

[Ian Bell]

Chuckle!  I get your point Rob.  But one thing at a time.   Gotta learn to
crawl before ya walk!  

Cheers,

Ian


-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of
Rob Mensching
Sent: December 2, 2015 00:34
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] how to debug/locate LGHT0001 error?

Or better yet use the stack trace to fix the bug in the WiX toolset itself
to print out a pretty error message instead of crashing when hitting an
apparent error case.
_____________________________________________________________
 Short replies here. Complete answers over there: http://www.firegiant.com/


-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of
Bob Arnson
Sent: Tuesday, December 1, 2015 8:40 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] how to debug/locate LGHT0001 error?

Comment out every file and uncomment them one at a time. Or do a binary
search instead.

> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On 
> Behalf Of Ian Bell
> Sent: Tuesday, 1 December, 2015 22:40
> To: 'WiX Toolset Users Mailing List' <wix-users at lists.wixtoolset.org>
> Subject: Re: [wix-users] how to debug/locate LGHT0001 error?
> 
> Hello Rob,
> 
> Thank you for suggesting the stack trace.   However, even when the VS2015
> 'MSBuild project build output' is set to diagnostic, the stack trace 
> also does not appear to provide any more information that can be used 
> to determine where the error has occurred (see stack trace example below).
> In
> the simple WIX project I created and which generates the error, there are
> only four WXS files and one WXI file.   If I was not aware that a string
> definition in the WXI file included one to many double quote 
> characters then the error message generate provides no real idea as to
which file the error
> occurred in as well as which character produced the error.   Other than
> rebuilding a WIX project in VS2015 from scratch, are there any other 
> techniques you could recommend that would help one to troubleshoot 
> such a problem?
> 
> Thank you,
> 
> Ian
> 
> 
> ==========================================================
> ======
> Stack trace generated when VS2015 MSBuild project build output is set 
> to
> diagnostic:
> 
> 5>		C:\Program Files (x86)\WiX Toolset v3.10\bin\Light.exe -out
> "C:\Users\Public\Documents\Visual Studio 
> 2015\Projects\Obfuscation\Solution\Deployment\SetupProject3\bin\Debug
> \SetupP
> roject3.msi" -pdbout "C:\Users\Public\Documents\Visual Studio 
> 2015\Projects\Obfuscation\Solution\Deployment\SetupProject3\bin\Debug
> \SetupP
> roject3.wixpdb" -v -cultures:null -ext "C:\Program Files (x86)\WiX 
> Toolset v3.10\bin\\WixNetFxExtension.dll" -contentsfile 
> obj\Debug\SetupProject3.wixproj.BindContentsFileListnull.txt
> -outputsfile
> obj\Debug\SetupProject3.wixproj.BindOutputsFileListnull.txt
> -builtoutputsfile
> obj\Debug\SetupProject3.wixproj.BindBuiltOutputsFileListnull.txt
> -wixprojectfile "C:\Users\Public\Documents\Visual Studio 
> 2015\Projects\Obfuscation\Solution\Deployment\SetupProject3\SetupProje
> ct3.wi
> xproj" -pedantic -v obj\Debug\InstallDirectories.wixobj
> obj\Debug\InstallationFiles.wixobj obj\Debug\Product.wixobj 
> obj\Debug\RegistrySettings.wixobj
> 5>		Windows Installer XML Toolset Linker version 3.10.1.2213
> 5>		Copyright (c) Outercurve Foundation. All rights reserved.
> 5>light.exe(0,0): error LGHT0001: Illegal characters in path.
> 5>		Exception Type: System.ArgumentException
> 5>		Stack Trace:
> 5>		   at System.IO.Path.CheckInvalidPathChars(String path,
> Boolean checkAdditional)
> 5>		   at System.IO.Path.IsPathRooted(String path)
> 5>		   at
> Microsoft.Tools.WindowsInstallerXml.BinderFileManager.ResolveFile(Stri
> ng source, String type, SourceLineNumberCollection sourceLineNumbers, 
> BindStage
> bindStage)
> 5>		   at
> Microsoft.Tools.WindowsInstallerXml.Binder.ResolveFields(TableCollecti
> on tables, Hashtable cabinets, ArrayList delayedFields)
> 5>		   at
> Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output output, 
> String databaseFile)
> 5>		   at
> Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output
> output, String file)
> 5>		   at
> Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args)
> 5>		Binder temporary directory located at
> 'C:\Users\admin\AppData\Local\Temp\4af5utmg'.
> 5>		Validator temporary directory located at
> 'C:\Users\admin\AppData\Local\Temp\mbfkjwc1'.
> 5>		The command exited with code 1.
> 5>	Done executing task "Light" -- FAILED.
> 5>Done building target "Link" in project "SetupProject3.wixproj" --
FAILED.
> 
> ==========================================================
> ======

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant
http://www.firegiant.com/