Not really, I also tried adding quotes in the form " instead of " but it failed.
I looked at http://windowssdk.msdn.microsoft.com/en-us/library/ms734147.aspx
and the only thing that may be a clue is: "Relative paths and environment variables cannot be used when specifying a file. A Universal Naming Convention (UNC) path can be used to locate the file. Any relative path and environment variable expansion needs to be done prior to creating the command.
> When building the Foundation part of th elibrary, I get the following error:
> Performing Custom Build Step
> MC: may only specify one message file to compile.
> The problem seems to be that I have spaces in the path name. So the solution is to move the library to say C: ,build it there and then move it back.
> Can this be fixed? I suspect that it is a simple matter of quoting the filename/paths for this particular command.