New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

light.exe fails even if the path does not contain unicode characters #5928

Open
MarekKosinski opened this Issue Jan 2, 2019 · 6 comments

Comments

Projects
None yet
2 participants
@MarekKosinski
Copy link

MarekKosinski commented Jan 2, 2019

Hi.

Please provide answers to the following questions to help us narrow down, reproduce, and fix the problem. Fill out one section and delete the others.

Bugs

  • Which version of WiX are you building with?
    I'm using WiX 3.11 released this on Dec 31, 2017.

  • Which version of Visual Studio are you building with (if any)?
    I'm using Visual Studio 2017 Community version 15.9.4.

  • Which version of the WiX Toolset Visual Studio Extension are you building with (if any)?
    I'm using Wix Toolset Visual Studio 2017 Extension version 0.9.21.62588

  • Which version of .NET are you building with?
    I'm using .NET Framework 4.5.2

  • Describe the problem and the steps to reproduce it.

I'm having a hard time creating my installer project. First off I had a problem that most things did not work if my project was located in C:/Users/Marek Kosiński/... because I had the Unicode in the path. The issue (#4923) helped me to realize that.
I've moved my project to C:\ and the project started to build properly. More problems started to appear when I've added files to install.

For example, when I add these lines:

  <Component Id="xxx.exe" Guid="f5140ff3-4f35-4e92-b193-24ab2c58fb3a">
    <File Id="xxx.exe" Name="G1ANT.Brain.UserRecorder.exe" Source="$(var.xxx_TargetDir)xxx.exe" />
  </Component>

I'm getting the very same exception as when my project was at C:\Users...
The exception is
The filename, directory name, or volume label syntax is incorrect. (Exception from HRESULT: 0x8007007B)

The visual studio is invoking:
4> C:\Program Files (x86)\WiX Toolset v3.11\bin\Light.exe -out C:\G1ANT.Brain\G1ANT.Brain.WixInstaller\bin\Debug\en-US\G1ANT.Brain.WixInstaller.msi -pdbout C:\G1ANT.Brain\G1ANT.Brain.WixInstaller\bin\Debug\en-US\G1ANT.Brain.WixInstaller.wixpdb -cultures:en-US -ext "C:\Program Files (x86)\WiX Toolset v3.11\bin\WixUIExtension.dll" -loc Common.wxl -contentsfile obj\Debug\G1ANT.Brain.WixInstaller.wixproj.BindContentsFileListen-US.txt -outputsfile obj\Debug\G1ANT.Brain.WixInstaller.wixproj.BindOutputsFileListen-US.txt -builtoutputsfile obj\Debug\G1ANT.Brain.WixInstaller.wixproj.BindBuiltOutputsFileListen-US.txt -wixprojectfile C:\G1ANT.Brain\G1ANT.Brain.WixInstaller\G1ANT.Brain.WixInstaller.wixproj obj\Debug\Components.wixobj obj\Debug\Directories.wixobj obj\Debug\Product.wixobj

and the next line is:
4>light.exe(0,0): error LGHT0001: The filename, directory name, or volume label syntax is incorrect. (Exception from HRESULT: 0x8007007B)

I'm using Windows 10, I don't know if that matters.

I'll be grateful for any tips on how to solve this issue or work around it.

@barnson

This comment has been minimized.

Copy link
Member

barnson commented Jan 3, 2019

What does $(var.xxx_TargetDir)xxx.exe evaluate to? If you can run Light.exe under the debugger, the exception should pop right up.

@MarekKosinski

This comment has been minimized.

Copy link

MarekKosinski commented Jan 3, 2019

xxx is G1ANT.Brain.UserRecorder

@barnson

This comment has been minimized.

Copy link
Member

barnson commented Jan 3, 2019

What's the full path?

@MarekKosinski

This comment has been minimized.

Copy link

MarekKosinski commented Jan 4, 2019

C:\G1ANT.Brain\G1ANT.Brain.UserRecorder\bin\Debug\G1ANT.Brain.UserRecorder.exe

@barnson

This comment has been minimized.

Copy link
Member

barnson commented Jan 4, 2019

It's probably not that path, then. You should try reproducing the problem while debugging Light.exe or using Process Monitor to track its i/o.

@barnson

This comment has been minimized.

Copy link
Member

barnson commented Jan 17, 2019

Any news? We're going to need you to reproduce the problem as it isn't happening elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment