Without this change, I get build errors when trying to use the MSBuild Community Tasks:
\Mac\Home\git-case-insensitive\acmeinc\acmeinc.productstructureeditor\src\Shells\ProductStructureEditorFeature10.0.1\ProductStructureEditorFeature10.0.1.csproj(238,5): error MSB4062: The "MSBuild.Community.Tasks.Xml.XmlQuery" task could not be loaded from the assembly \Mac\Home\git-case-insensitive\acmeinc\acmeinc.productstructureeditor\src\packages\MSBuildTasks.1.5.0.235\build\\..\tools\MSBuild.Community.Tasks.dll. Could not load file or assembly 'file://\Mac\Home\git-case-insensitive\acmeinc\acmeinc.productstructureeditor\src\packages\MSBuildTasks.1.5.0.235\build\\..\tools\MSBuild.Community.Tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
Please note that the path contains \\, which is likely to cause the problem. MSBuildThisFileDirectory already contains a trailing slash, at least in my scenario.
Applying this change in the .targets file in my local NuGet packages folder makes the build succeed. My workstation is a Parallels VM running on macOS, with a Windows 7 VM running Visual Studio 2017.
Without this change, I get build errors when trying to use the MSBuild Community Tasks:
Please note that the path contains
\\, which is likely to cause the problem.MSBuildThisFileDirectoryalready contains a trailing slash, at least in my scenario.Applying this change in the
.targetsfile in my local NuGet packages folder makes the build succeed. My workstation is a Parallels VM running on macOS, with a Windows 7 VM running Visual Studio 2017.