Path Too Long errors

microsoft.public.dotnet.framework

25 Jan 2006 3:20 PM

SGibson

Is it possible to surpass (or get around) the 260 character full path
limitation for File/IO type operations using .NET? For corporate
environments, particularly when working with file servers where users store
their files, it is not uncommon to run into situations where users have been
overly verbose in their naming of files and directories. The "path too long"
error that results when trying to work with these files is a real
show-stopper.

Any help on this issue? Suggested work-arounds (preferably not involving
p/invoke)? Please?

-Steve

PS: I know in the Win32 API there are "wide" versions of various IO
functions (i.e. CopyFileW() as opposed to CopyFile()) which allow one to use
a URI path designation that has a limit of around 32000 characters for the
path rather than 260.