P/Invoke differences (.NETCF 2.0)

G

Guest

Hello,

are there any differences when importing DLLs via P/Invoke with the .NETCF
2.0?
I tried out the "P/Invoke Library Sample" from Microsoft which uses the
..NETCF
1.0. I deploied this application to my pocketpc and everything works fine.
For example reading the call-log gives me the correct amount of
dialed/received calls with the correct dates.

But if i try to use the *same* source code (e.g. the class "phone.cs") in my
own pocketpc application which is using *.NETCF 2.0* some functions do not
work. Reading the call-log now only gives me the correct amount of
dialed/received calls. Instead of showing me the correct dates there is only
a defaultvalue (01-01-01) listed.

Now i am wondering how that can be, because it is the same source code,
which imports the same DLL (phone.dll) and i deploied it to the same
pocketpc. Only the version of the used compact framework changed from 1.0 in
the original MS-app to 2.0 in my app.

Has anybody an idea what this can be?

Thanks a lot!
 
G

Guest

There could be a bug in the code that isn't affected by CF 1.0, but CF 2.0's
marshalling, which is more strictly defined, has a problem with it.

-Chris
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top