Long paths support (its easy..probably!)

[Pr0FiT]

I've seen in older posts that longs paths (261+ characters) were not supported by the app BUT i thought it might be a good idea to revisit this since you're half way there already.

Looks like you're at .net 4.7 which does support long paths so it should be as simple as adding the below to the manifest. I *believe* there would be no side-effects for non-supported OS's or W10 users that do not have the gpo setting enabled. What do you think?

 

	<asmv3:application xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
		<asmv3:windowsSettings
			 xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
			<dpiAware>True/PM</dpiAware>
			<longPathAware xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">true</longPathAware> <!-- Insert me here or somebody is getting a lump of coal this christmas -->
		</asmv3:windowsSettings>
	</asmv3:application>

 

Docs: https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx?f=255&MSPPError=-2147217396#maxpath

 

[oblivioncth]

Yes this is a grave dig, but i just ran into an issue due to LB not having long paths support: Any folder that has but a single file with a path over the original limit (260 char) is ignored when trying to import files. I have quite long path names because of the massive amount of ROMs I have and I like them to be quite organized. For the time being I have gotten around this issue with copious use of junctions/symbolic links, but it would be quite nice if I could avoid all of that in the future.

This was in 10.8 beta 2.

Since the OS handles the path name resolution, it should only require a slight change in the source for LB, possibly just the manifest like the OP said to enable the app to make use of long path names for users of Windows 10 who have that enabled.

Edited December 24, 2019 by oblivioncth

[johnsanc]

I just ran into this issue today as well. The interesting thing is that LaunchBox apparently tries to resolve to a long path, but the app still doesn't seem to support it. The error message that comes up for a network share with a long path shows "\\?\UNC\[server]\" which is the correct syntax for UNC long paths. I know this isn't an OS issue since I can open the very long path file in Dolphin no problem and I have opted into long paths with a registry update. Info here: https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file

@Jason Carr - Can you please see if its as easy as a config to fix this? This has apparently been an issue for two years.

Edited December 24, 2019 by johnsanc

[oblivioncth]

7 hours ago, johnsanc said:

I just ran into this issue today as well. The interesting thing is that LaunchBox apparently tries to resolve to a long path, but the app still doesn't seem to support it. The error message that comes up for a network share with a long path shows "\\?\UNC\[server]\" which is the correct syntax for UNC long paths. I know this isn't an OS issue since I can open the very long path file in Dolphin no problem and I have opted into long paths with a registry update. Info here: https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file

@Jason Carr - Can you please see if its as easy as a config to fix this? This has apparently been an issue for two years.

Interesting. Makes me worried that Jason already did flip the switch and that the implementation is somewhat broken on Microsoft's end depending on the particular libraries/options used when the app is built; even if it isn't that exactly, something dumb that would be a pain to isolate :/.

Feel free to vote for the issue here: https://bitbucket.org/jasondavidcarr/launchbox/issues/5097/feature-request-longpath-support

[johnsanc]

Here is the error in the debug log:

2019-12-24 12:45:34 PM FIRST CHANCE EXCEPTION: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
   at System.IO.PathHelper.GetFullPathName()