Palm OS Programming, 2nd Edition

Using Conduit Inspector to Verify Your Conduit

Now it’s time to tell you what to do if you have problems with your conduit: use the Conduit Inspector, which is part of the CDK. With the Conduit Inspector, you can examine a conduit DLL and verify that it:

• Is registered correctly

• Has the right entry points

• Implements those entry points correctly

You can run the Conduit Inspector manually, or from the HotSync application.

Running the Conduit Inspector Manually

To run the Conduit Inspector manually, you should execute:

C:\CDK402\Common\Bin\C4.02\ConduitInspector.exe

From the File menu, choose Open and select your conduit.

The Conduit Inspector will display information about the conduit and will also open Dependency Walker, a third-party tool that is included with Visual Studio (this tool shows what DLLs the conduit depends on—see http://www.dependencywalker.com for full details). You can use Dependency Walker to verify that all the needed DLLs are present. This is especially important because HotSync will silently ignore your conduit if it depends on a missing DLL.

Warning

When you first open the Conduit Inspector, it may be unable to find the Dependency Walker. To fix this problem, run the Dependency Walker by hand once (using Start → Programs → Microsoft Visual C++ → Microsoft Visual C++ Tools → Depends). Having run it once, the Conduit Inspector seems to be able to find it from then on when necessary.

Running the Conduit Inspector from the HotSync Application

You can also run the Conduit ...