So what's your reasoning behind not wanting to P/Invoke? Do you realize
that even the CF libraries P/Invoke, since that's the only way to call the
OS APIs. Sticking to purely .NET with CF 1.0 will yield to one of 2 things:
a severly crippled and featureless application that any competitor can
quickly beat or the realization that a managed CE application cannot provide
much meaningful use without calling APIs currently not wrapped by the
Compact Framework.
P/Invocation should not be feared. It's not some arcane, magical or
mystical craft reserved for those with pointy hats and wands. Understanding
P/Invoke simply requires understanding how the managed an unmanaged worlds
of code communicate with one another. Learning that facet will actually
make you a better developer and help you in your debugging skills.
-Chris
[quoted text, click to view] "Mansour Ghaoui" <Mansour Ghaoui@discussions.microsoft.com> wrote in message
news:E6354325-2D60-4DE2-9296-5E9EEE88732F@microsoft.com...
>I am currently exploring .NET and Windows mobile devices. I've downloaded
>all
> the necessary SDK and I can easily build and deploy .NET applications to
> my
> T-Mobile SDA.
>
> When I read the help files, I get brief tutorials on how to make a simple
> WinForms application. But I'd like to access the functions of the phone
> (SMS,
> bluethooth, make phone calls).
>
> When I read further I get a lot of infomation about P/Invoke. But I don't
> want to use P/Invoke, I want to stick purely to .NET.
>
> My question is: How limited is the library? What classes are implemented
> and
> what not? Can I find a web page or help file that gives me detailed
> information of which classes are implemented and how to use them?
>
> Thank you.
>