Long path handling

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

PGomersall

229 discussion posts

Jon,
I often do searches on drives that act as profile servers. Folders on them often included AppData\Roaming. Often FileSeek has problems with files that are from web sites - and have extremely long file names\paths. FileSeek does not seem to be able to handle these. Is this a bug or design limitation that is known about and has plans to be fixed - or something else?
Pete

Aug 18, 2011 • #1

I'll check with Jon, but I believe it's not something we can fix, due to the 260 character file path limit in Windows: http://msdn.microsoft.com/en-us/library/aa365247%28v=vs.85%29.aspx#maxpath

Aug 19, 2011 (modified Aug 19, 2011) • #2

Just followed up with Jon and yeah, it's due to a limitation in the .NET API, so unfortunately we can't fix it

Aug 19, 2011 • #3

PGomersall

229 discussion posts

Jon and Keith,
Why can't you code the applications logic to check for path length and switch to UNC style prefex - \\?\ if greater than 260?
Pete

Aug 19, 2011 • #4

I'm not sure that all the underlying .NET functions support the UNC style long paths either. This would be something that we would need to investigate further. FileSeek relies on many file system API calls to work (including the IFilter calls), and I'm not sure all of them support >260 chars.

Aug 19, 2011 • #5

PGomersall

229 discussion posts

Thanks for the time both of you.
Something to investigate though as it would improve the application?
Pete

Aug 19, 2011 • #6

For sure, we'll definitely look into it some more when we get a chance.

Thanks!

Aug 19, 2011 • #7

PGomersall

229 discussion posts

Quote:

(Removed)

This seems like a bit of advertising for a tool that is not free?
Pete