Cheers guys.
Sashman, thanks for the link, but it costs 499 bucks for a 1 year dev licence... not exactly what I was hoping for....
When I said I didnt want to use PINVOKE, what I meant was, I want to access an object in a managed framework, not have to use unmanaged techniques inside my app with all the complications at runtime that it can bring. OK, I take it on board that the compact framework is just that, but bearing in mind the importance of networking especially in todays computing, I am a little surprised that there are no add-on api's that could be bolted on to support hardware such as the IPAQ and HTC mobiles (or any system using mobile PC as an OS)... Interop is not an elegant solution in my mind.
The whole point surely of the .net framework and operating in an OO manner is surely that you use objects without knowing what is going on in the background, all the PINVOKE type stuff, Binary as well as error handling that causes all sorts of problems to the developer.
I programme on Java for example, I look up my handset, (W810i for example) I see the following online:
http://developer.sonyericsson.com/site/global/products/phonegallery/w810/p_w810.jsp
Java Micro Edition (Java ME)
CLDC 1.1 (JSR 139)
MIDP 2.0 (JSR 118)
Wireless Messaging API (JSR 120/205)
Mobile Media API (JSR 135)
Java Technology for the Wireless Industry (JSR 185)
Java API for Bluetooth

(JSR 82)
PDA Optional Packages for
J2ME Platform (JSR 75)
Web Services (JSR 172)
I can see that if I program an app, I have access to the underlying bluetooth stack, PDA functionality (calendar, email etc) wireless messaging and its all done in a manner that means I can programme in an OO manner in JAVA ME.
Compare this to the microsoft 'experience'... I have hardware that ONLY runs with Windows Mobile edition, yet, I have NO access to the bluetooth stack OBEX etc without doing messy unmanaged code...
I LOVE the .net framework, its an easy to understand, easy to use programming language that has lots of potential. BUT, and its a big one, Java and objective-C are FAR more easy to programme with when you start wanting to interface with hardware. Surely a company such as MS could set up standards based hardware requirements for its software and help manufacturers out with this.
Mobile 7 looks really promising. Microsoft need to learn however that having a beautiful looking, quick OS running on a good quality pleasant looking mobile is one thing. The Iphone is not successful because of this. The Iphone kicks A$$ because of the proprietary apps you can download from small developers. The Iphone however is lacking in one area. Microsoft Exchange. If Windows come up with an OS that supports bluetooth, wireless and MS Exchange access, then NOW we are talking.
(as another aside, why no MS exchange API yet again? No MAPI support and no means easily sending/recieving mail via MS exchange via .net framework??)
Now, I am not naieve. If MS are honest, I bet they would say the proprietary paid-for APIs do exactly what I am asking for. I bet MS make big bucks from all those MSDN subscriptions too. But dont then wonder why Apple kicks MS into the grave when their Mobile 7.0 OS flops against the competition put up from Apple. MS have a real opportunity here to create functionality that will destroy blackberry and apple to boot as a result. All developers need are free APIs to programme with, not dynamic objects and a whole host of other arbritary upgrades to C# 4.0 which I cant really be bothered to go out and purchase VS 2010 for. If MS come up with the APIs, I will come up with the cash for a new Developer Studio.
Edit:
Oh, MS, just whilst I am ranting, why no decent graphing/charting APIs? why do I have to pay the likes of Dundas mega-bucks to put a bar chart in an app?
So, in summary microsoft, to give Steve Jobs a good kicking:
Windows Mobile 7 to ship to Mobiles which have standardised hardware to software support
Support for OO access to Bluetooth, Wireless and PDA style apps (calendar object access, contacts access, mobile funcitonality access), plus some form of BASIC grapahing/charting object (so we dont annoy our MSDN and MSDN Gold certified Dundas buddys off now).
Easy object oriented access to MS exchange server via existing network objects and above bluetooth or wireless objects or mobile GPRS connection.
IMPORTANT ONE!!! Access to GPS functionality on the mobile device with decent, useful methods.
A MS appstore with online training and support for $50 annual membership. This is key. Apple have gotten this completely right in limiting the apps that get put onto the Iphone. Profits come from sharing 40%/60% with the developer from downloads and recurrent licencing.
That is all! I am sure the worlds largest software manufacturer will not struggle with developing the goods!