Long File Paths

From: "James Simpson" <JamesSimpson@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Sun, 29 May 2005 01:46:03 -0700

Hello,
I was wondering how I would go about handling large file paths (greater than
the regular 200 and something character limit for file paths). I read an
article on MSDN regarding this and they said I have to use the Unicode
version of their respective libraries (for creating a directory for instance
using CreateDirectory), however when I attempt to use their suggestion it
appears that I am not using the Unicode libraries. How would I go about
forcing the compiler to look for and find libraries that support long path
names (Unicode)? Is it a part of the Platform SDK?

Sincerely,

James Simpson
Straightway Technologies

.

Follow-Ups:
- Re: Long File Paths
  - From: David Lowndes

Prev by Date: how to free the excrescent memory
Next by Date: Re: Dialog fonts
Previous by thread: how to free the excrescent memory
Next by thread: Re: Long File Paths
Index(es):
- Date
- Thread

Relevant Pages

Re: sources/Build.exe alternate source file location question
... >> either compile the individual source modules or also use libraries. ... >Yes, well, there are also shared header files, which can't be compiled ... Header file paths are not a problem. ... >> code base out as a separate module under your SCMS, and share it out of the ...
(microsoft.public.development.device.drivers)
Re: sources/Build.exe alternate source file location question
... >> either compile the individual source modules or also use libraries. ... >Yes, well, there are also shared header files, which can't be compiled ... Header file paths are not a problem. ... >> code base out as a separate module under your SCMS, and share it out of the ...
(microsoft.public.win32.programmer.kernel)