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
We've got a C# project where the .less compilation isn't working for one of our developers (set as a build action on the .less file and working for other developers using the same project).
From what I can tell the problem is that his Windows username contains a space, so his checked out less file is at C:\Users\First Last\Documents\GitHub\Project\Project\Website\Content\less\project.less
The output he gets when building includes:
lessc: ENOENT, open 'C:\Users\First Last\Documents\GitHub\Project\Project\Website\Content\less\Last\Documents\GitHub\Project\Project\Website\Content\css\project.css.map'
My initial thought is that the "build from" parameter is not being quoted / escaped properly before being passed to the build script, but I'm not sure where that happens.
The text was updated successfully, but these errors were encountered:
@iant-tui, You might want to try upgrading the NuGet package. I am not getting this error anymore on my copy and I see that I am quoting all of the parameters. Does he have any special characters in his first or last name that could be causing the issue besides the space?
We've got a C# project where the .less compilation isn't working for one of our developers (set as a build action on the .less file and working for other developers using the same project).
From what I can tell the problem is that his Windows username contains a space, so his checked out less file is at C:\Users\First Last\Documents\GitHub\Project\Project\Website\Content\less\project.less
The output he gets when building includes:
lessc: ENOENT, open 'C:\Users\First Last\Documents\GitHub\Project\Project\Website\Content\less\Last\Documents\GitHub\Project\Project\Website\Content\css\project.css.map'
My initial thought is that the "build from" parameter is not being quoted / escaped properly before being passed to the build script, but I'm not sure where that happens.
The text was updated successfully, but these errors were encountered: