The PathFindOnPath function is anything but special. Whatever it does, can be accomplished by using FILE() and GETENV() FoxPro functions. Though it gives me a chance to demonstrate a technique of assembling an array of strings for being passed to external function.
More comments below the source code.
usingSystem;
usingSystem.Text;
usingSystem.Runtime.InteropServices;
namespace WinAPI.SearchPath{class Class1
{/*
EntryPoint="PathFindOnPathA" means that the function expects
strings in one byte per character format. PathFindOnPathW must
be used otherwise.
System.Text.StringBuilder Class represents a string-like object.
Its value can be modified once it has been created
by appending, removing, replacing, or inserting characters.
In the code below the upper limit of 260 characters is set
for the new instance of the StringBuilder.
The last member of dirs, the array that stores directory names,
must be null. Omitting this, triggers an exception,
System.NullReferenceException, if the file name is not found.
*/constint MAX_PATH = 260;
[STAThread]staticvoid Main(){
StringBuilder f = //file to be searchednew StringBuilder("test.txt", MAX_PATH);
//directories to be searched firststring[] dirs = {"c:\\dir1",
"c:\\dir2", "c:\\documents\\dir1", null};
Console.WriteLine(PathFindOnPath(f, dirs) ?
f.ToString() : "File not found");
Console.ReadLine();
}[DllImport("shlwapi.dll", EntryPoint="PathFindOnPathA")]staticexternbool PathFindOnPath(System.Text.StringBuilder pszFile,
string[] ppszOtherDirs);
}}
The second parameter of the PathFindOnPath is a memory address of null-terminated array of pointers to strings. Members of such array must be 4-byte numbers, format called UINT or DWORD. Each array member is an address of allocated in memory string that contains a directory name.
In this code sample, I want to make this function search for the file in three directories:
c:\dir1
c:\dir2
c:\documents\dir1
As the first step, I use the GlobalAlloc to allocate each directory name in memory. Three GlobalAlloc calls return three memory addresses.
To become a null-terminated array, these memory addresses must be put one after another to a memory buffer and padded by some null characters. As I said, each address must occupy four bytes.
So far these numbers are in FoxPro numeric format. This is something similar to managed objects in .Net. Technically I can not say how many bytes each numeric value takes and where exactly it resides in memory.
Somehow I need to convert them to 4-byte DWORDs. Three addresses, as three directories are searched, and five zero bytes, produce the total length of 17 bytes. I use num2dword() function to convert each number to 4-character string, which is the binary character representation of the DWORD format. In VFP9 you probably can use BINTOC() for this conversion.
So now I have created the binary character representation for the array -- a string 17 characters long. I could use the GlobalAlloc again to allocate this string in memory and obtain its address.
But more elegant solution is declaring this parameter as STRING @ -- a reference to a string, cPathArray in the code above. That makes the FoxPro to take care about all memory operations: memory allocation, passing the pointer to the PathFindOnPath and releasing the memory in the end.
PChar class hides certain complexity of memory API calls. In particular, it calls the GlobalFree, whenever a PChar instance is destroyed or re-allocated, preventing memory leaks.
Credits: PHP (4.4.9), an HTML-embedded scripting language,
MySQL (5.1.55-log), the Open Source standard SQL database,
AceHTML Freeware
Version 4, freeware HTML Editor of choice. Hosted by Korax Online Inc.