Long filename support

[NotNull]

This is what Everything's application manifest looks like:

Code: Select all

<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
        	manifestVersion="1.0"
        	xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
	<assemblyIdentity version="1.0.0.0"
                		processorArchitecture="*"
                		name="Everything"
                		type="win32"/>
	<description>Everything Search Engine</description>
	<dependency>
		<dependentAssembly>
			<assemblyIdentity type="win32"
                				name="Microsoft.Windows.Common-Controls"
                				version="6.0.0.0"
                				processorArchitecture="*"
                				publicKeyToken="6595b64144ccf1df"
                				language="*"/>
		</dependentAssembly>
	</dependency>
	<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
		<security>
			<requestedPrivileges>
				<requestedExecutionLevel level="asInvoker"
                       					uiAccess="false"/>
			</requestedPrivileges>
		</security>
	</trustInfo>
	<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
		<application>
			<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
			<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
			<supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
			<supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
			<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
		</application>
	</compatibility>
	<asmv3:application>
		<asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
			<dpiAware>true</dpiAware>
		</asmv3:windowsSettings>
	</asmv3:application>
</assembly>

There is no reference to long filename support, like

Code: Select all

<windowsSettings xmlns:ws2="http://schemas.microsoft.com/SMI/2016/WindowsSettings">
        <ws2:longPathAware>true</ws2:longPathAware>
</windowsSettings>

Not needed? Not added because of support for older Windows versiions?

[void]

I will consider enabling this.
Thank you for the suggestion.

I wonder what this does with shell extensions...
Will this make shell extensions blow up more?
I will need to test.

For now, Everything is long path aware.
Everything will automatically prefix long paths with \\?\