Or can I expect to be able to call BT apis, gps service in control panel, etc.

Specifically interested in WM Professional. It can be very  hard ferreting 
out this kind of info.

 Thanks

 mike

The CF can't be "crippled" as it can be installed in the field.  Obviously 
device-specific stuff might not be there (i.e. GPS stuff won't be there on a 
device with no GPS), and there are no .NET bluetooth interfaces in the CF 
(see 32feet.net).


-- 

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com




"Mike Klein" <Mike Klein@discussions.microsoft.com> wrote in message 
news:5ACCB2BC-A50A-4853-BEE3-8C5309571039@microsoft.com...

> Or can I expect to be able to call BT apis, gps service in control panel, 
> etc.
>
> Specifically interested in WM Professional. It can be very  hard ferreting
> out this kind of info.
>
> Thanks
>
> mike 

I don't believe this is necessarily true unless you know it to be.

It w/be trivial for hooks in .NET Compact framework to check for presence of 
carrier or other certificates and only enable certain functionality 
selectively, no?

I would be surprised if MS isn't courting carriers with ability for these 
restrictions as J2ME is setup exactly this way. Carriers currently...although 
most don't...have the ability to restrict unsigned cab files.

Carriers aren't exactly embracing advanced capabilities on their networks.

Do the restrictions I am mentioning (if they indeed exist) apply only to 
2-tier smartphones or single-tier WMProf phones too?

thanks for help.

>I don't believe this is necessarily true unless you know it to be.


I know it to be true.  What indicates otherwise?


> It w/be trivial for hooks in .NET Compact framework to check for presence 
> of
> carrier or other certificates and only enable certain functionality
> selectively, no?


It would be if they wanted it, but there are no such hooks.


> I would be surprised if MS isn't courting carriers with ability for these
> restrictions as J2ME is setup exactly this way. Carriers 
> currently...although
> most don't...have the ability to restrict unsigned cab files.


For what benefit to Microsoft?  The carrier can decide what can and cannot 
run through signing and API lockdowns at the OS level.  They don't control 
the CF.


> Carriers aren't exactly embracing advanced capabilities on their networks.


Depends on the carrier.  And I can see their side too - we do wacky stuff as 
develoeprs at times.


> Do the restrictions I am mentioning (if they indeed exist) apply only to
> 2-tier smartphones or single-tier WMProf phones too?


The OEM of any device has a lot of options on what they can do.  Currently 
the 2-tier phones are the only ones that carriers are really prone to 
locking down (though most can be unlocked or purchased unlocked anyway).


-- 

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com