Provide Consistent, Up-to-date Windows Support

[This is preliminary documentation and subject to change.]

Providing consistent, up-to-date support for Windows standards and technologies makes your application easier to use and administer, and helps to avoid incompatibility problems.

Designed for Microsoft® Windows® Logo requirements that relate to this goal are listed below. The list is just a summary. To qualify for the Designed for Windows Logo, you must comply with all stipulations of the requirement reference text to which the list refers.

General

• Meet all requirements on the latest releases of Windows NT and Windows 95. (Required)
• Support multiple platforms. (Required)
• Make your application stable and fully functional. (Required)
• Make your application 32-bit. (Required)
  • Identify 16-bit legacy versions clearly. (Required)
• Support multiTasking. (Required)
• Support standard system settings. (Required)

File System

• Do not assume a hard-drive size limit of 2 GB.
• Support the Universal Naming Convention (UNC).

  Exception: Non-File-Based Applications are not required to provide UNC support

• Support long file names for files exposed to users.
• Support long file names for files exposed in Windows Explorer.
• Use long file names in user-interface elements.
• Test LFN functionality on Windows NT FAT, NTFS, and compressed NTFS partitions.

Operating System Migration

• Provide a Migration DLL where necessary.

Accessibility

• Be compatible with the High Contrast option.
• Provide keyboard access to all features.
• Document the keyboard user interface.
• Provide notifications of the keyboard focus location.

  Exception: Development tools and Java Applications are temporarily exempt from the requirement to expose the keyboard focus.

Internet Security

• Digitally sign ActiveX controls.
• Support Authenticode signing of downloadable code.

OLE / COM

• Provide an OLE container or object server.

  Exception: Non-File-Based Applications and Java Applications are not required to provide OLE support.

• Allow users to drag objects to any container.

  Exception: Development Tools are not required to provide drag-and-drop support within the tool's design environment.

• Implement IDropTarget and/or IDropSource interfaces in containers .

  Exception: Development Tools are not required to provide drag-and-drop support within the tool's design environment.

• Test object servers for basic OLE functionality.
• Test containers for basic OLE container functionality.
• Place an Object command on a container's Insert menu.

Telephony

• Use TAPI for telephony.
• Use the Assisted Telephony interface in telephony-enabled applications.
• Implement the full TAPI interface in telephony-centric applications.
• Apply dialing properties to numbers in telephony-centric applications.
• Allow a user to select the calling device in telephony-centric applications.
• Share serial devices properly in telephony-centric applications.
• Explicitly link to a TAPI32 Library if using TAPI 2.x.
• Gracefully degrade to work with TAPI 1.4 from TAPI 2.x.

OnNow / ACPI

• Handle system Sleep-Wake transitions properly.