GetLongPathName API Function Emulation
Posted
by Randall Garacci
on November 12th, 2002
The GetLongPathName API call is only available on Windows 98/ME and Windows 2000/XP. It is not available on Windows 95 & NT. This code example emulates the function for use on 95 & NT and will work on the other systems as well.
This example uses MFC and CString, but could be easily adapted to use null terminated character strings as well. The algorithm recursively strips off path components, then reassembles them with their long name equivalents.
DWORD GetLongPathName(CString strShortPath,
CString& strLongPath )
{
int iFound = strShortPath.ReverseFind('\\');
if (iFound > 1)
{
// recurse to peel off components
//
if (GetLongPathName(strShortPath.Left(iFound),
strLongPath) > 0)
{
strLongPath += '\\';
if (strShortPath.Right(1) != "\\")
{
WIN32_FIND_DATA findData;
// append the long component name to the path
//
if (INVALID_HANDLE_VALUE != ::FindFirstFile
(strShortPath, &findData))
{
strLongPath += findData.cFileName;
}
else
{
// if FindFirstFile fails, return the error code
//
strLongPath.Empty();
return 0;
}
}
}
}
else
{
strLongPath = strShortPath;
}
return strLongPath.GetLength();
}

Comments
Error CloseHandle for
Posted by Fthr on 10/24/2011 02:45am"When the search handle is no longer needed, close it by using the FindClose function, not CloseHandle." As you can see on link http://msdn.microsoft.com/en-us/library/windows/desktop/aa364418(v=vs.85).aspx
ReplyThanks for your idea! I tweaked your code a bit.
Posted by n0gsg on 06/06/2006 08:58pmRandall, Thanks for your code tip, very nicely done! I added two minor fixes: 1) Changed the code so that it will correctly parse long filenames on network shares (for example, the name "\\server_name\share\myfile.txt" will fail to parse in the original code since "\\server_name" won't successfully pass the ::FindFirstFile() call. 2) Added HANDLE variable 'h' so that the resulting file handle can be closed to prevent a leak. Tom ///////////////////////////////////////////////////////////////////////////// // // DWORD GetLongPathName(CString strShortPath, CString& strLongPath) // // Stupid Microsoft bandaid - allows GetLongPathName emulation under W95. Needed // since XP transmits filenames in short form, while // 95/98/2000/NT don't, but function not available to // fix problem under 95. // // From: http://www.codeguru.com/cpp/w-p/files/article.php/c4461/ // Author: Randall Garacci // // Parameters: [in] strShortPath -- The mangled short pathname to the file // [out] strLongPath -- The calculated long pathname // // Returns: 0 on failure, or the length of the calculated long pathname // // Revision history: // // 06/06/2006 -- Wheeler, T: Added code to correct HANDLE leak & modified // (iFound >1) test to allow parsing a file on a network share. // ///////////////////////////////////////////////////////////////////////////// DWORD GetLongPathName(CString strShortPath, CString& strLongPath ) { HANDLE h; int iFound = strShortPath.ReverseFind('\\'); if ((iFound > 1) && (strShortPath.Left(2) != "\\\\")) // Added 06/6/2006 { // recurse to peel off components // if (GetLongPathName(strShortPath.Left(iFound), strLongPath) > 0) { strLongPath += '\\'; if (strShortPath.Right(1) != "\\") { WIN32_FIND_DATA findData; // append the long component name to the path // if (INVALID_HANDLE_VALUE != (h=::FindFirstFile(strShortPath, &findData)) ) { ::CloseHandle(h); strLongPath += findData.cFileName; } else { // if FindFirstFile fails, return the error code // strLongPath.Empty(); return 0; } } } } else { strLongPath = strShortPath; } return strLongPath.GetLength(); }ReplyAn alternative method which is also suitable for all flavours of Windows
Posted by Legacy on 11/14/2002 12:00amOriginally posted by: Jase Jennings
ReplyThanks...
Posted by Legacy on 11/12/2002 12:00amOriginally posted by: Paul Selormey
Just tested it, it works!
Thanks for the contribution.
Best regards,
ReplyPaul.