4 ms·
I agree, but there are two different issues here (1) \\?\ to bypass the maximum path length limitation; (2) \\?\ to bypass the reserving of file names for devic
by skissane 5y ago
I agree, but there are two different issues here (1) \\?\ to bypass the maximum path length limitation; (2) \\?\ to bypass the reserving of file names for devices
You are talking about (1), and I agree it has some problems, yet Microsoft already has an EXE manifest option to bypass maximum path length without \\?\.
Whereas, I am proposing (2), which could exist without (1). They could add an EXE manifest option and/or registry key to tell the Win32 API to ignore bare device names, or device names with extensions, when converting Win32-to-NT paths, even while keeping the MAX_PATH limitation. So you wouldn't need \\?\ to access a file/directory with a reserved device name. But you might still need it to access a long path. The two issues are orthogonal and could be controlled by different settings.
- int_19h 5y agoOh, I see. Yes, the ability for an app manifest to opt out of device names being special would certainly make sense.