Windows Mobile 6 SDK Refresh — Professional & Standard: What’s New for Developers

Windows Mobile 6 SDK Refresh — Professional & Standard: What’s New for Developers

Microsoft’s Windows Mobile 6 SDK Refresh (Professional & Standard) updates the developer toolset for building and testing applications targeting the refreshed Windows Mobile 6 platforms. This article summarizes the key changes, new assets, compatibility considerations, and practical steps to start using the refreshed SDKs.

What’s included in the refresh

• Updated Device Emulators — New emulator images that match final platform builds more closely, including updated ROMs and device profiles for both Professional (touch) and Standard (non-touch) editions.
• Platform Tools & Libraries — Revised platform DLLs and updated headers to reflect bug fixes and behavioral changes in the OS refresh.
• Samples & Documentation — New and updated sample projects demonstrating best practices for touch interaction (Professional) and hardware key navigation (Standard), plus refreshed API notes and troubleshooting tips.
• Testing & Debugging Enhancements — Improved emulator integration with Visual Studio (⁄₂₀₀₈ supported), faster deployment, and fixes to debugging scenarios that previously required device resets.
• CAB/Deployment Updates — Sample CAB creation tweaks and guidance for handling installer behaviors specific to the refreshed OS build.
• Localization & Regional Builds — Additional localized emulator images and resources to aid testing for international deployments.

Why it matters for developers

• Behavioral parity with shipped devices: The refresh emulators and updated platform files reduce surprises caused by minor OS differences between early SDKs and shipping device ROMs.
• Faster debugging and iteration: Emulator fixes and Visual Studio integration improvements shorten development cycles.
• Migration stability: Developers maintaining apps across WM5 → WM6 transitions gain clearer guidance and compatibility fixes.
• Better sample coverage: Updated samples show recommended patterns for UI, power management, and connectivity under the refreshed OS behavior.

Compatibility and system requirements

• Visual Studio 2005 or 2008 is required for native and managed Windows Mobile development with these SDKs.
• Windows host OS: Windows XP SP2 or later (check exact refresh release notes for any additional patches).
• .NET Compact Framework: The refresh includes guidance for CF versions supported by WM6; ensure your development machine has the matching CF redistributables for accurate testing.

Key developer impacts and migration notes

• API stability: No major API removals are introduced in the refresh, but some behavioral adjustments (timing, input handling) may require small app fixes—particularly for UI responsiveness and hardware key handling on Standard devices.
• Touch vs. non-touch differences: Professional SDK samples emphasize tap/gesture patterns; Standard samples show focus and D-pad navigation. Verify UI flows on both emulator types.
• Installer behavior: CAB installation quirks on refreshed ROMs may affect permissions and installation targets—test CABs on the new emulators and on representative hardware.
• Performance testing: Use updated emulators to re-run performance and memory tests; small OS-level fixes can change memory footprint and responsiveness.

Quick start: install and test in 5 steps

1. Download both Professional and Standard SDK Refresh installers from Microsoft’s developer download center (or your archived MSDN resources).
2. Install Visual Studio ⁄₂₀₀₈ and required .NET Compact Framework versions if not already present.
3. Run SDK installers; restart Visual Studio to pick up new device targets and emulators.
4. Open an updated sample project from the SDK, build, and deploy to the appropriate emulator (Professional for touch, Standard for keypad).
5. Exercise installation (CAB), input (touch/key), and connectivity scenarios; note any behavioral differences and consult the SDK release notes for known issues.

Troubleshooting & where to look first

• Emulator fails to start: ensure virtualization/emulator prerequisites and that required OS patches are present.
• Debug deployment errors: verify Visual Studio Device Center connectivity, remove stale emulator instances, and reboot the host if necessary.
• UI input issues: compare behavior between Professional and Standard emulators and consult sample code for recommended patterns.
• CAB install problems: check manifest/INF settings and test on both emulator and physical device builds.

Where to find more information

• SDK release notes included with the refresh — primary source for detailed changes and known issues.
• Updated samples in the SDK — practical references for patterns and fixes.
• Microsoft developer forums and archived MSDN articles for community patches and troubleshooting tips.

Quick checklist for release readiness

• Rebuild and test all supported binaries against the refreshed SDK emulators.
• Verify installer behavior (CAB) and runtime permissions.
• Test input flows separately on Professional (touch gestures) and Standard (hardware keys) emulators.
• Run performance and memory regression checks.
• Update documentation and deployment instructions to reflect any install or runtime differences discovered.

If you want, I can produce a step-by-step checklist tailored to a specific app type (e.g., .NET Compact Framework vs. native C++) or generate sample CAB and deployment scripts for the refreshed SDKs.