You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The execution currently fails if using WSL and the username contains spaces. This is due to improper escaping of space characters in GitExe and CygPathExe.
Steps to Reproduce
Create a Windows username with spaces on the name, so its .nuget folder is in a path that contains spaces, such as C:\Users\Example User\.nuget\packages\gitinfo\2.2.0\build.
Attempt to run a project that has GitInfo setup.
On the output console the following will be displayed:
4>"C:\Users\Example" is not recognized as an internal or external command,
4>operable program or batch file.
4>C:\Users\Example User\.nuget\packages\gitinfo\2.2.0\build\GitInfo.targets(1088,3): warning MSB3073: Command "..." exited with error code 9009.
4>"--version" is not recognized as an internal or external command,
4>operable program or batch file.
4>C:\Users\Example User\.nuget\packages\gitinfo\2.2.0\build\GitInfo.targets(203,3): warning MSB3073: Command "..." exited with error code 9009.
4>C:\Users\Example User\.nuget\packages\gitinfo\2.2.0\build\GitInfo.targets(212,3): error : Failed to run `git --version`. Git may not be properly installed:
4>C:\Users\Example User\.nuget\packages\gitinfo\2.2.0\build\GitInfo.targets(212,3): error : "--version" is not recognized as an internal or external command,;operable program or batch file.
Expected Behavior
GitInfo should run just fine.
Version Info
Present in latest 2.2.0
The text was updated successfully, but these errors were encountered:
Describe the Bug
The execution currently fails if using WSL and the username contains spaces. This is due to improper escaping of space characters in GitExe and CygPathExe.
Steps to Reproduce
C:\Users\Example User\.nuget\packages\gitinfo\2.2.0\build
.On the output console the following will be displayed:
Expected Behavior
GitInfo should run just fine.
Version Info
Present in latest 2.2.0
The text was updated successfully, but these errors were encountered: