Forum Discussion
Publishing a self-hosted pipeline on MacOS with dotnet issues
JoostdeboerThe issue was solved. I had the path to the file that was being called, and this path contained a space. Inputting the path did not attach quote marks around it, so it was being read as separate files, and thus produced an error. I've fixed the path string to contain no more spaces, instead attaching the words with underscores, and the error disappeared.
If anyone knows of a way to fix it by making the command ran on the pipeline always use quotation marks, that would be good to know as well, but for now I've found a way to solve it.
JoostdeboerThe issue was solved. I had the path to the file that was being called, and this path contained a space. Inputting the path did not attach quote marks around it, so it was being read as separate files, and thus produced an error. I've fixed the path string to contain no more spaces, instead attaching the words with underscores, and the error disappeared.
If anyone knows of a way to fix it by making the command ran on the pipeline always use quotation marks, that would be good to know as well, but for now I've found a way to solve it.