> Thanks, Geoff, I've been trying for a long time to get info on that. I'm
> not clear on why this would cause my conduit to crash. Is it that it makes
> calls that crash if MFC 4.1 is not loaded?
Well, I'm not exactly sure what causes the crash at the moment, either. We know
that a percentage of conduits that use the Palm41.dll (ie - old conduits that
were built using CDK 2 or earlier) cause this crash with HotSync 3.0.3. This
didn't show up in our backward compatibility testing because not all old
conduits had this problem (testing old conduits with the new HotSync version).
> I understand that to say: "If you're using CDK 3.0 or later, you don't have
> to worry about Palm41.dll, and if you're using CDK 3.0 or later, here's what
> you have to do." Either it is a typo, or it is not clear. Do you mean to
> say
>
> "If your conduit was built using CDK 2 or earlier, consider the following
> information."
I guess this is a little confusing. Basically, if developers have a conduit that
was originally developed using CDK 2 or earlier, we really want them to update
them to be built using CDK 3 or later. Once you do this, your conduit should not
require Palm41.dll. (plus... we reduce the risk of problems like this not
showing up in our testing)
Now, migrating a conduit from CDK 2 to a later version requires the following
steps:
1. Make sure your conduit is built as a regular DLL, and not an MFC Extension
DLL. Recommend using the Wizard in the CDK to generate a starter project, then
copy your source files from the old conduit into the new project. Just be
careful that the Conduit entry points like InitInstance(), ExitInstance(),
CfgConduit(), and GetConduitInfo() are migrated to the new structure appropriate
for a regular DLL, or appropriate for HotSync 3.0 or later.
2. Implement GetConduitInfo() as indicated in the previous e-mail.
3. Just check to make sure you are not linking old versions of the Palm
Libraries like tables20.lib and pdcmn20.lib. These should be tables21.lib and
pdcmn21.lib, if your conduit requires them. If you used the Wizard in step 2 to
generate a template, you shouldn't have to worry about this step. The reason why
I mention this is that if you just take a project built using CDK 2 and
re-compile it under CDK 3 or later, it will still link in the old libraries,
since you will just use the old project settings.
Sorry about the length of these messages. This may be more information than you
need. I am kind of guessing that you created your conduit using CDK 2 or earlier
and I needed to give details about how to migrate them to the latest CDK.
-Geoff Richmond
Developer Support
Palm, Inc.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
