Freigeben über


Credential Manager Migration (Windows CE 5.0)

Send Feedback

The following items are important to understand when you migrate an OS design that uses credential manager:

Migrating from Windows CE .NET 4.2 to Windows CE 5.0

The credential manager APIs in Windows CE 5.0 are not backward compatible with the APIs in Windows CE .NET 4.2. It is recommended that all applications that use the older APIs migrate to the Windows CE 5.0 set of APIs.

Although the Windows CE .NET 4.2 API set is deprecated, it is still supported. However, future versions of Windows CEmay not have the continued support for older versions of the API set.

Effective with Windows CE 5.0, the following changes were made to Credential Manager:

  • Header file Credmgr.h is replaced with Cred.h.
  • Link library Secur32.lib is replaced with Coredll.lib.
  • CREDENTIAL structure is replaced with CRED, and the following changes apply:
    • CRED_FLAGS_PROMPT_NOW is deprecated. To get the same behavior, set pBlob member to NULL in the new CRED structure.
    • LastWritten is deprecated. There is no equivalent in the new CRED structure.
  • CeCredRead function is replaced with CredRead.
    • Target in CeCredRead is ignored. Default target (L"") is assumed.
  • CeCredWrite function is replaced with CredWrite.
    • Target in CeCredRead is ignored. Default target (L"") is assumed.
    • Credentials are always marked with CRED_FLAG_DEFAULT.
  • CeCredFree function is replaced with CredFree.

In addition to changes in the API set, there are also changes in the credential manager infrastructure that affect Network User Interface (NetUI). These may be used to define configuration settings for the Network and Dial-up Connections icon in Control Panel. For more information, see Network User Interface Migration.

For general migration information, see Migrating from an Earlier Version of Windows CE.

See Also

Credential Manager | Credential Manager Functions | Network User Interface Migration

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.