fix: Changed WorkingDirectory to $(OutDir) as default and $(OutputPath) as fallback

[Brimerland]

Exec WorkingDirectory should be $(OutDir) as default and $(OutputPath) as fallback.
$(OutputPath) might not work on large complex solutions.

See https://github.com/dotnet/msbuild/blob/f914c9bfb613d32edb658b803c7fe046f9ee3c37/src/Tasks/Microsoft.Common.CurrentVersion.targets#L107-L122

'OutDir and OutputPath are distinguished for legacy reasons, and OutDir should be used if at all possible.'

Experienced this error in my solution where $(OutDir) is used.

Calling dscom.exe to export type library
P:\code\packages_installed\dspace.runtime.interopservices.buildtasks\1.7.0\build\dSPACE.Runtime.InteropServices.BuildTasks.Tools.targets(64,5): error MSB6003: The specified task executable "cmd.exe" could not be run. System.IO.DirectoryNotFoundException: The working directory "bin\x64\Debug\net8.0-windows\win-x64\" does not exist.
P:\code\packages_installed\dspace.runtime.interopservices.buildtasks\1.7.0\build\dSPACE.Runtime.InteropServices.BuildTasks.Tools.targets(64,5): error MSB6003:    at Microsoft.Build.Tasks.Exec.GetWorkingDirectory()
P:\code\packages_installed\dspace.runtime.interopservices.buildtasks\1.7.0\build\dSPACE.Runtime.InteropServices.BuildTasks.Tools.targets(64,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.GetProcessStartInfo(String pathToTool, String commandLineCommands, String responseFileSwitch)
P:\code\packages_installed\dspace.runtime.interopservices.buildtasks\1.7.0\build\dSPACE.Runtime.InteropServices.BuildTasks.Tools.targets(64,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands)
P:\code\packages_installed\dspace.runtime.interopservices.buildtasks\1.7.0\build\dSPACE.Runtime.InteropServices.BuildTasks.Tools.targets(64,5): error MSB6003:    at Microsoft.Build.Tasks.Exec.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands)
P:\code\packages_installed\dspace.runtime.interopservices.buildtasks\1.7.0\build\dSPACE.Runtime.InteropServices.BuildTasks.Tools.targets(64,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.Execute()

Also there were quotation marks missing causing an exit code 9009 (file not found) on calling the dscom tool if it is located in a path containing spaces.

This Pull Request fixes these issues.

[SOsterbrink]

Thank you for your contribution and the good explanation.

[Brimerland]

Do I need to do something here?
The unit test failed without showing any errors except these two lines:
"The active test run was aborted. Reason: Test host process crashed"
"Error: Process completed with exit code 1."
And my commits did not change anything which is unit testable.

[SOsterbrink]

Do I need to do something here? The unit test failed without showing any errors except these two lines: "The active test run was aborted. Reason: Test host process crashed" "Error: Process completed with exit code 1." And my commits did not change anything which is unit testable.

There should not be a problem. Somehow the test process crashed on the build machine. I'll have to take a closer look if that persists. For now I just restarted the unit tests.