koobas.hobune.stream
Is there an accepted solution to allow file paths longer than 260 characters?
Our application (a Windows standalone player) uses data that is frequently stored by users at paths that are longer than the Windows limit. I have tried several methods to access data at long file paths to no avail:
Prepending "\\?\" to the file paths (causes a stack overflow when Directory.CreateDirectory is called)
Opening [PlayerName].exe in a text editor and setting longPathAware to true in the manifest (results in a side by side configuration error due to "incorrect XML syntax" even though an XML parser cannot find any errors and the xmlns values have been verified to be correct)
Following the instructions at https://forum.unity.com/threads/windows-standalone-custom-exe-manifest.972900/ (couldn't load the WindowsPlayer project in Visual Studio, plus I have a custom build script)
Has anyone successfully handled long file and directory paths? Target .NET Framework version is 4.7.1.
