Supposed source code assembly mismatch prevents breakpoints from being hit

I followed the Offroad Debugging of .NET Core on Linux OSX from Visual Studio wiki to set up remote debugging with VS 2017. Everything was pretty successful except for the following error about a source code assembly mismatch.

If I pause in the debugger, the symbols seem to load fine, but I can’t tell from where using the Modules window. Even after I pause, breakpoints don’t get hit.

I used scp to copy bin/Debug/netcoreapp1.1/ from linux to windows, I tried adding the windows directory I copied to as a "Symbol file (.pdb) location in Visual Studio's Options dialog. This wasn't necessary in VS 2015, and doesn't seem to help in VS 2017

I can work around this issue by unchecking “Require source files to exactly match the original version”, so this is a pretty minor issue, but I didn’t have to do this in VS 2015. I also don’t want to forget to recheck this option in the event I attach to a local process.

Start from the reported remote-debugging setup for .NET Core with VS 2017, including the copied bin/Debug/netcoreapp1.1 files and the Visual Studio Modules and symbol settings. Reproduce the source mismatch and breakpoint failure, then compare the behavior with VS 2015; done means matching source files load without disabling exact matching and breakpoints are hit.