Currently, we perform no path normalization in the AssignPackagePath task, and this means we can easily end with mixed paths, making it difficult to tell apart which are the same, and when comparing via code, having to take into account the possibility that there might be a mixture.
To simplify things, we should normalize all paths to use the / forward slash which is more compatible for cross-platform projects, is already supported universally in MSBuild as well as NuGet, and entirely avoids having to do \\ double slashes for escaping (or @ literals) in code.
Currently, we perform no path normalization in the
AssignPackagePathtask, and this means we can easily end with mixed paths, making it difficult to tell apart which are the same, and when comparing via code, having to take into account the possibility that there might be a mixture.To simplify things, we should normalize all paths to use the
/forward slash which is more compatible for cross-platform projects, is already supported universally in MSBuild as well as NuGet, and entirely avoids having to do\\double slashes for escaping (or@literals) in code.