Windows Mobile SDK: Questions Please!

I started working on a FAQ to go into the Windows Mobile SDK, and I wanted to start to cover as many of those "Hmm, how do I....?" questions as possible.

Initially I thought, "I know, I'll just look in the newsgroups and see what the most common questions are", but then - whoohoo! - there are a <b>lot</b> of them, and every question - while very, very important to the person asking it - is so specific it may not actually help anyone else.

So lets limit the scope a little to start with - what questions did you have when you were starting to develop in Windows Mobile? What information could we have given you that would have made things just that little bit easier?



Comments (9)
  1. Paul L says:

    How about a list of shortcut keys that Windows Mobile supports? I can’t seem to find a list documenting them anywhere! (Such as how to select an auto-suggested word with the keyboard while typing!)



  2. macbirdie says:

    I’ve always been wondering what were the Win32 API limitations in comparison to desktop Windows systems. GDI, crypto, COM, input, shell, communication (sockets, wininet etc) and others. Also, what’s been added in all those areas.

    How do I unleash the full potential of the Windows Mobile platform and an applications created for it? What do I get that’s better than in a desktop?

    What are the things I have to think different about when designing and developing a WM application?

    How do I get access to the GSM terminal on a low level in order to e.g. get some info on the GSM cells I’m in range with, and other AT commands, if possible.

    Also, articles on creating ActiveSync (and WMDC) sync providers and custom SIPs are not very beginner friendly. 😉

    Just a few I came up with in the last few minutes. 😉

  3. Peter Foot says:

    I’ve found a few areas frustrating in the documentation:-

    Features which are documented in the Windows CE SDK, are present in the Windows Mobile platform but which are not documented in the Windows Mobile SDK, such as SMS Providers and lots of Bluetooth OS Functions.

    A whole area which I find is lacking in documentation is CEMAPI. There are still some contradictory points (PR_BODY / PR_SUBJECT for SMS) and items which are important to using MAPI which are not documented well – storage of email body, mime support etc. Also IMAPIAdviseSink – depending on how you read the documentation it doesn’t support a whole load of event types like newmail.

    Thirdly something I have noticed with the SDK documentation is that lots of topics are missing from the Table of Contents even though they are present. You can get to them through other links and Search but it would be quicker to use the TOC if you know what you are looking for.

  4. MSDN Archive says:

    Wow, these are great questions guys – thanks very much.

    Some of these are just holes in the docs: I’ll bring them to the attention of the authors.

    Some are topics that should be present in the SDK, but aren’t due to an oversight. I’ll try to get these sorted.

    Some are errors that happened during our last docs update. Peter: yes, the table of contents got messed up. We’re fixing it. It should be better.

  5. JohnGuin says:

    How to create setup projects – this is consistently a nightmarish experience.

  6. Dave Kees says:

    My Microsoft Technology Center developer told me that it is not possible to use C# to use the functions of both Excel and the SMS. (I’m trying to develop an Office Automation program where people can send an SMS to access specific data contained in Excel cells on a WM phone, receiving the data in an SMS message.) Is that correct?

  7. MSDN Archive says:


    Well, you can intercept SMS messages:

    But I don’t believe you can query Excel. At least, not easily. Perhaps storing data in Excel isn’t the best way to do it – sounds like maybe a little database application might be better?

  8. Quang says:

    Dear John,

    I am developing an application which can send SMS message from a PC to another PDA. Everything that I have on my PC are VS2005, Windows Mobile 6, Microsoft ActiveSync.

    These code below I wrote to test, please let me know if it true or false. In my application, I have a textbox which can type the phone number ( to ), and textarea which used to write contents.

    These are my code for a button ( when I click IM button ):



     Contact contact = new Contact();

     contact.MobileTelephoneNumber =


     SmsMessage sms_message = new SmsMessage();

     sms_message.Body = this.txtMsg.Text.Trim();

     OutlookSession os = new OutlookSession();


     if( os.SmsAccount == null )


       throw new ArgumentException(" The account is not         initialized ");



     MessageBox.Show(" Your SMS message will come soon ");


    catch( SmsException smsex )


      MessageBox.Show( smsex.Message );


    catch( Exception ex )




    Is it true or false? If false, could you show me, please?

    I search on Internet too much, and find some solutions from many other developers.

    1. Use GSM modem

    2. Through ISP

    I don’t know if it has many solutions. Hope you can show me.

    Thank you very much


  9. Gary Davis says:

    I get the error above. This is the build of a newly created project:

    —— Build started: Project: DeviceApplication2, Configuration: Debug Any CPU ——

    DeviceApplication2 -> c:ProjectsDeviceApplication2DeviceApplication2binDebugDeviceApplication2.exe

    —— Deploy started: Project: DeviceApplication2, Configuration: Debug Any CPU ——

    The system cannot find the path specified.

    ========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========

    ========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

    My system is Windows Server 2003 SP2.

    I have Visual Studio 2005; I had Windows Mobile 5.0 Pocket PC SDK; I tried a repair and an un-install and re-install, all still produced the error (I have no idea what file is attempted be opened). I installed the Mobile 6.0 Standard SDK and still the same issue.

    Also installed are Microsoft .NET Compact Framework 1.0 SP3 Developer; Microsoft .NET Compact Framework 2.0 SP2; Normal Framework 2.0 & 3.0; Microsoft Device Emulator 1.0;

    Thanks for your help. I search google on the error message and did not find anything useful.

    Gary Davis

Comments are closed.

Skip to main content