Toluu

Windows Mobile Team Blog

The Official Windows Mobile Team Blog

BCross promoting PDCOctober 3

Brian, the creator of WiMo, one of great Windows Mobile Devs helping out with PDC 2008:

http://channel8.msdn.com/Posts/PDC-2008-is-cominghellip-and-I-canrsquot-wait/

I bet you will read his blogs from a completely different perspective after you see the video!

Good job Brian!

 -Luis Cabrera

Adding a signature to a message account (setting properties on message accounts)September 27

Hi!

For those of you with WIndows Mobile 6.1 devices, you might notice that your Activesync emails all automatically have signatures. We've gotten requests from partners wanting to do add/modify the signature to an account as well.  Here is a sample function to update the signature for the Activesync account.  Error checking removed in this sample code :).

#include <atlbase.h>
#include <cemapi.h>

HRESULT AddSignatureToAccount()
{
    HRESULT hr;

    CComPtr<IMAPITable> ptbl;
    CComPtr<IMAPISession> pSession;
    CComPtr<IMsgStore> pMsgStore;

    // Log onto MAPI
    hr = MAPILogonEx(0, NULL, NULL, 0, static_cast<LPMAPISESSION *>(&pSession));

    // You can open a different message store here instead of the default
    hr = pSession->OpenMsgStore(NULL, 0, NULL, NULL, 0, &pMsgStore);

    SPropValue rgspv[3] = { 0 };

    rgspv[0].ulPropTag      =   PR_CE_SIGNATURE;    // signature content
    rgspv[0].Value.lpszW    =   L"Sent from my personal Windows Mobile phone";
    
    rgspv[1].ulPropTag      =   PR_CE_USE_SIGNATURE;    // use the signature in newly composed emails
    rgspv[1].Value.b        =   TRUE;
    
    rgspv[2].ulPropTag      =   PR_CE_USE_SIGNATURE_REPLY_FORWARD;    // use signa

Trouble getting your ActiveSync provider to work with Windows Mobile Device Center?September 9

As most of you know, ActiveSync has been replaced by a new app called Windows Mobile Device Center (WMDC) on Vista. I occasionally hear from developers who have problems getting their ActiveSync Sync Service Providers (SSPs) to work with WMDC. Usually its a registration issue and the error messages aren't very helpful.

I have a fix that I'd like to share with developers facing such problems. It's a very minor fix and has worked every single time I've suggested it to someone. Here's what you need to do: In the SSP's CLSID InprocServer32 regkey, add a string named "ThreadingModel" with the value "Apartment".

That's it. By doing this, in almost all cases your ActiveSync provider should work just fine with WMDC. Hope this little tip helps any developer struggling with WMDC issues.

-Mel

Which icon sizes should I use in my application?August 14

We've covered icons in the past, but I thought it was a good idea to review this information because I often see applications that use incorrect icon sizes. At a high level, here are the icon sizes Windows Mobile developers need to be aware of:

Windows Mobile Professional and Classic devices (formerly known as "Pocket PC"):

• Normal DPI: 16x16 (small) and 32x32 (large)
• High DPI: 32x32 (small) and 64x64 (large)

Windows Mobile Standard devices (formerly known as "Smartphone"):

• Normal DPI: 16x16 (small) and 32x32 (large)
• High DPI: 22x22 (small) and 44x44 (large)

So which of these icons should you use and where?

Application icons:

Your application's main icon (the first one embedded inside your .exe) is used in various places such as File Explorer, Task Manager, Start menu shortcuts, 3rd party memory management utilities etc. Since you cannot predict or control whether the user will see this as a large or small icon, you should support the maximum number of sizes for this icon (i.e. both small and large formats).

If you are creating a single .exe that is designed to run on all Windows Mobile devices, use an application icon with these sizes:

• 16x16
• 22x22
• 32x32
• 44x44
• 64x64

If your .exe is only designed for "Pocket PC" devices, use an application icon with these sizes:

• 16x16
• 3

Introducing the Windows Mobile API Usage Tool!August 3

I'm really excited to announce the release of the Windows Mobile API Usage Tool, available here: http://www.microsoft.com/downloads/details.aspx?FamilyID=fc803c7b-e855-475a-b8f3-38c19a007d36&displaylang=en

 The API Usage Tool scans your Windows Mobile applications (in cab, msi, or binary formats), performs static analysis, and reports on the usage of APIs and other system resources.  Our application compatibility team has been using the tool for several months now to ensure that we have good coverage of our public SDK when we do testing with 3rd party applications, as well as to help guide resource allocation and investments toward the most frequently used APIs.

 The tool includes a file-- deprecated.txt-- that has the current list of deprecated APIs for Windows Mobile, and will report on your application's usage of these APIs.  It's a really effective way to evaluate how your application will be affected once these deprecated APIs are removed from Windows Mobile.

 The tool is command-line based, and its output is a SQL Compact Edition database (.sdf file).  When used with the /deprecated option, the tool will also generate a collection of useful reports.

 We're hoping that developers find the tool and reports useful, and we'r