I spent two hours scratching my head today because I had put

  "/path/to/thing/**" 

in a nuspec file instead of

  "\path\to\thing\**"

The backslash was escaping the wildcard characters :(

On interactive uses, sure. But it's not clear cut, some code paths are lower level and bypass that.

Yea I guess most of my uses have been in things like python (e.g. open() and as.*). Got any examples of code paths that bypass that check and fail if you use /?

I think they are wrong and actually it's the opposite problem. Some applications and libraries that do their own path mangling on Windows will choke if you give them a /. The win32 file I/O API handles them correctly.

Never use windows, why should you for development and deployment?