How to turn project's target from PocketPC to WinCE?

[datamodel]

I'm having trouble porting my PPC (PocketPC) application to a Windows
CE 4.2 device.
I get a LoadType or TypeLoad exception right at application startup.
We've double checked the correct SDK cabs are installed on the CE
device,
as well as the references in the project.
But still no go.
Any suggestions or help ?
Thanks .

 

[Chris Tacke, eMVP]

Sounds like you're using a library not in your CE device's image. Check to
see what major functionality blocks you're using and ensure that support is
in the underlying OS. Focus on the PPC-specific stuff.

--
Chris Tacke
Co-founder
OpenNETCF.org
Are you using the SDF? Let's do a case study.
Email us at d c s @ o p e n n e t c f . c o m
http://www.opennetcf.org/donate

 

[datamodel]

The application runs fine on the WinCE emulator (default) though also
the debugger doesn't show any problems.
On the physical device I get a Managed TypeLoadException occuring at
frmMainMenu::.ctor+0x17

 

[Chris Tacke, eMVP]

First, the emulator and a physical device are not the same. Second, does
your device have all the components that emulator image has? Third, did you
try to debug this? You're getting a trappable exception in the ctor of your
Form - what is that line of code doing?

--
Chris Tacke
Co-founder
OpenNETCF.org
Are you using the SDF? Let's do a case study.
Email us at d c s @ o p e n n e t c f . c o m
http://www.opennetcf.org/donate

 

[Paul G. Tobey [eMVP]]

And what emulator are you using? Windows CE is *not* some sort of
monolithic OS where every copy on every device has the same capabilities.
If you are using the Windows CE emulator in VS.NET 2003, that means
*absolutely nothing* about whether the actual target device will work. If
you are using an emulator *for the specific target device*, then it should
match the feature set on the real device and you'll need to contact the
device OEM for help. You can build a Windows CE image with *no UI at all*,
so obviously, displaying forms isn't going to work on such a device!

Paul T.

 

[datamodel]

The line at which the exception occurs instantiates the database
interface class.

Deployments to The device's emulator fail.
I see the point that the VS.NET2003 "default" CE emulator is useless
since the problem is most likely device specific (Symbol MC3000)

Thanks for your replies.

 

[datamodel]

I think the problem probably has to do with what I'd like to call
SDK cab hell.
I'm not 100% sure that i'm using the right SQLCE,Symbol SMDK,
OpenNetCF,
and core .NET cabs for the Symbol MC3000 running WinCE 4.2.

But when installing those, I didn't get the "this SDK is not compatible
with this operating system" message that I got with other cabs (the
wrong ones).

I'll just stick with the Symbol site pages for now to see again if i'm
using the wrong SDKs.

On a more general tone. This "SDK cab hell" is uber-frustrating
considering that i'm porting a MICROSOFT .net app from MICROSOFT's
PocketPC "platform"
to MICROSOFT's winCE. It's ridiculous that MS technologies don't
readily work with themselves.

If we were developing in java. Deployment to different devices and
platforms, wouldn't be so some troublesome, when it really should be
trivial and effortless.