dotnet does not appear to require a trailing backslash when you define a custom NuGet package cache path via env var NUGET_PACKAGES but Visual Studio does.
@bradwilson the bad case also leads to paths being written with \ in editorconfig. That is problematic as it breaks path comparisons in the compiler and other tooling
@jaredpar I assume the answer is replacing string-concatenated paths with Path.Combine. More typing for more safety. MSBuild files tend to be all about the string concatenated paths. 😔
@bradwilson
The inconsistency around the trailing (back)slash is one of the most annoying things. First I need to remember if it's forward or backward on the system I'm currently on, 😂then I ALSO need to remember if there's one at the end or not (sigh). Have these people writing these things not heard of, you know, standards? 😂
Add comment