If you are used to static linkage, or DLL linkage with lib files, then the DLL linkage used for PathEngine may
seem a little strange initially,
but arranging the linkage in this way has the advantages of encapsulating each SDK release in a single file
and ensuring clean and robust operation against changing versions of the SDK.
Explicit LoadLibrary() calls are preferred over lib files because this enables run-time reloading of the DLL
and ensures that the client application has full control of the DLL location and loading process.

The DLL linkage setup also makes it possible to do things like switching in an instrumented
query logging wrapper dll without recompiling the main application.

Obtaining an entry point

Note that the following instructions only apply to the full version of the SDK.
'TestBed only' versions of the SDK do not contain a standalone version of the PathEngine dll.

Use the Win32 function
LoadLibrary()
(or LoadLibraryEx())
to load pathengine.dll, and then the Win32 function
GetProcAddress()
to obtain a pointer to PathEngine's entrypoint.