pinvoke WM5

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have posted this before but I am not sure where I left off and I am still
having an issue with it.

I have the exact same code that works on Windows Mobile 5 Pocket PC Ed. on
two different Ipaqs and a Palm Treo Phone.

I create a SmartPhone build for the same stuff and everything works fine
except pinvoke throws an exception claiming there is a "Missing Method".

Is there any special differences between SmartPhone version and Pocket PC
version for pinvoking a custom dll?

Thank you very much.
 
Well I mean like the following:

[DllImport("MyDLL.dll",CharSet=CharSet.Unicode,SetLastError=true)]
public static extern bool MyMethod();

where I define in my native dll:

extern "C" {
MYDLL_API BOOL MyMethod();
};
 
Well, if you're sure that your native DLL is in a suitable location and that
the missing method exception isn't being thrown because of an error on your
part, it could be a lack of your application and DLL being signed and the
SmartPhone locked. I would expect that it's more likely to be your fault
for that particular exception, though.

Paul T.

Jeremy said:
Well I mean like the following:

[DllImport("MyDLL.dll",CharSet=CharSet.Unicode,SetLastError=true)]
public static extern bool MyMethod();

where I define in my native dll:

extern "C" {
MYDLL_API BOOL MyMethod();
};

Paul G. Tobey said:
Not in how you do it, but in what APIs are available, yes.

Paul T.
Click to expand...
Click to expand...
 
I have the dll alongside the application in the same directory although it is
invisible on the device itself I can see it using windows explorer on my
desktop. Someone mentioned it needed to be in the Windows directory so I
tried copying it there and that didnt work either. Like I said it works
perfect on Pocket PC edition, just not SmartPhone.

Jeremy said:
Well I mean like the following:

[DllImport("MyDLL.dll",CharSet=CharSet.Unicode,SetLastError=true)]
public static extern bool MyMethod();

where I define in my native dll:

extern "C" {
MYDLL_API BOOL MyMethod();
};

Paul G. Tobey said:
Not in how you do it, but in what APIs are available, yes.

Paul T.
Click to expand...
Click to expand...
 
Well, when all of the possible explanations are exhausted, start with the
impossible. Signing is the first thing that comes to my mind, anyway. You
might try testing that by writing a *native code* application to call that
DLL and see what happens with it.

Paul T.

Jeremy said:
I have the dll alongside the application in the same directory although it
is
invisible on the device itself I can see it using windows explorer on my
desktop. Someone mentioned it needed to be in the Windows directory so I
tried copying it there and that didnt work either. Like I said it works
perfect on Pocket PC edition, just not SmartPhone.

Jeremy said:
Well I mean like the following:

[DllImport("MyDLL.dll",CharSet=CharSet.Unicode,SetLastError=true)]
public static extern bool MyMethod();

where I define in my native dll:

extern "C" {
MYDLL_API BOOL MyMethod();
};

Paul G. Tobey said:
Not in how you do it, but in what APIs are available, yes.

Paul T.

I have posted this before but I am not sure where I left off and I am
still
having an issue with it.

I have the exact same code that works on Windows Mobile 5 Pocket PC
Ed. on
two different Ipaqs and a Palm Treo Phone.

I create a SmartPhone build for the same stuff and everything works
fine
except pinvoke throws an exception claiming there is a "Missing
Method".

Is there any special differences between SmartPhone version and
Pocket PC
version for pinvoking a custom dll?

Thank you very much.
Click to expand...
Click to expand...
Click to expand...
 
I see it now I wasnt signing the dll properly.

Thanks for pointing me in the right direction.

Paul G. Tobey said:
Well, when all of the possible explanations are exhausted, start with the
impossible. Signing is the first thing that comes to my mind, anyway. You
might try testing that by writing a *native code* application to call that
DLL and see what happens with it.

Paul T.

Jeremy said:
I have the dll alongside the application in the same directory although it
is
invisible on the device itself I can see it using windows explorer on my
desktop. Someone mentioned it needed to be in the Windows directory so I
tried copying it there and that didnt work either. Like I said it works
perfect on Pocket PC edition, just not SmartPhone.

Jeremy said:
Well I mean like the following:

[DllImport("MyDLL.dll",CharSet=CharSet.Unicode,SetLastError=true)]
public static extern bool MyMethod();

where I define in my native dll:

extern "C" {
MYDLL_API BOOL MyMethod();
};

:

Not in how you do it, but in what APIs are available, yes.

Paul T.

I have posted this before but I am not sure where I left off and I am
still
having an issue with it.

I have the exact same code that works on Windows Mobile 5 Pocket PC
Ed. on
two different Ipaqs and a Palm Treo Phone.

I create a SmartPhone build for the same stuff and everything works
fine
except pinvoke throws an exception claiming there is a "Missing
Method".

Is there any special differences between SmartPhone version and
Pocket PC
version for pinvoking a custom dll?

Thank you very much.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top