I don't see how this helps in the commonly reported case where folks are opening projects off mapped drives. This checks __filename, which is the currently executing file (i.e. tsserver.ts), which is likely installed locally with the editor (or plugin), not on the mapped drive where a project may live.

agree with @billti - the issue here is that case-sensitivity can vary between mounted volumes.

Maybe it makes more sense for the useCaseSensitiveFileNames value to be a project property instead of a host property, because as pointed out it may vary from project to project.

Agree it makes more sense per project. I would test whatever the first file loaded for a project is (whether that be a .ts/.js file or the tsconfig.json file), as I doubt one project would be spread across volumes with different case sensitivity (and if they are... too bad).

Close in light of #7658