Actually, reading back over your original message, my reply would have been
exactly what it was.  When you say 5.0, that does not read as WM 5.0 to me
at any time or in any way (and there is no such thing as WM 5.0, anyway,
best I can tell).  I'd still say that 2540 *is* a course for 5.0.  Obviously
I come at this as a device OEM and not a software-only guy, so that's my
device-builder bigotry.

I'm sure that the limitation is at MSL, as far as reading the tea leaves on
what training is required, but my own feeling is that most people can get
started pretty much without training if they really are software guys.  It's
hard to convince them that they need training, even when they do, *once*
they've gotten started.  I think that, in most cases, this is actually a
*good* thing, as it indicates that the tools themselves don't require much
training and it's the track to complex applications that needs to be greased
a little and not the track to simple, hello world, or even basic data access
applications, that need training to implement.  I think that the training
market is for porting from .NETCF 1.0/CE4.x/WM2003 to .NETCF 2.0/CE5/WM5 is
very, very small and I can't say that I blame MSL for ignoring it, if they
are.

Paul T.