Right Microsoft, first post here.. I am a fairly new c# programmer who has self-taught over the past 2-3 years.. (i know.. i know... work long hours and only get to code in free time).
I am fairly complicit with using all of the C# features up to 2.0 and can use some of the labda function/anon delegate c# 3.5 stuff. Thats for the background. Now, to my question.
Why, Oh why, do microsoft not release a SUPPORTED .net object oriented Bluetooth API or at least support manufacturers that may wish to provide an API with their product? I dont particularly want to go down the unmanaged code route, as I was hoping that .net would at some stage develop a decent Bluetooth API... PARTICULARLY for .net compact framework.
Same with wireless support... Why no wireless API?!?!?
.net has the potential to become the modern pocket computer programming language of choice, yet Java and Coffeebeans offer much more functionality...
So, whats the official line microsoft? Are there competition issues wrt smaller developers producing rediculously overpriced APIs that the home developr cannot afford? Or is such a change to the framework in the pipeline? I would MUCH prefer simple Bluetooth and Wireless functionality as opposed to the largely abstract changes that have been brought in sharp 4.0...
I DONT WANT TO HAVE TO USE PINVOKE INSIDE AN OO MANAGED PROGRAMMING LANGUAGE!
Regards,
Paul Flusk
