I have a T-Mobile MDA which says in the system info that it's running Windows Mobile 5.0 and that it's a Pocket PC.

I thought I should be creating Windows Mobile 5.0 projects, but it seems that it can also run Pocket PC 2003 projects.

When I load the bluetooth chat program I have more success with the PPC2K3 version than any other - does this mean that some of my phone's information is wrong?

Cheers,

Matt. W.

The fundamental difference between a WM5.0 Pocket PC project and a Pocket PC 2003 project is that the WM5.0 project will have access to the Managed Microsoft.WindowsMobile.* assemblies. Otherwise they use the same .NETCF version etc so you can deploy a PPC2003 project to a WM5.0 device (the reverse is true if you use no Windows Mobile 5.0 specific features).

Peter

So I should be building my projects as WM5.0, not PPC, because there'll be more assemblies available?

I only ask because I'm getting the same error (the one you answered in the bluetooth forum) on btListener.Start() no matter what I do.

Thanks for all the help,

 Matt.

I'm no a CE guy so this is my best understanding...  In brief,our CE1 library cannot be used from a NETCFv2 application. :-(  We will fix this sometime...

When one creates a new project of either of those types (PPC2k3/WM5) then one gets offered NETCFv2 and NETCFv1 templates, with the latter having a (1.0) in their name as I remember.  This isn't terribly obvious post hoc either, v2 projects have a Signing tab on the Project properties, v1 don't and also have an "Upgrade project" option on their menu, the XML in the vbproj/csproj file is different too.

Any chance that the C# project you created is v2 but referencing CE1 and thus won't work, and the supplied VB sample is v1 referencing V1 which is fine.

Thankyou so much! I had not realised what the extra digits were for; of course now it seems so simple.

I copied the code I was using into a new V1 project and all worked fine.

Thanks again,

 Matt.

Cool.  The other option of course is to create a V2 project and reference the CE2 version of the library.  It depends on what configurations of CE device you are targetting, whether they will have NETCF v1 or  v2 present.  There's lot of nicer stuff in v2 versus v1, Generics, lots more classes/methods, C# anonymous methods etc.

We'll fix that bug sometime soon and that issue won't be a problem anymore.