Kris Kumar
09-25-2005, 01:30 PM
<div class='os_post_top_link'><a href='http://msdn.microsoft.com/mobility/default.aspx?pull=/library/en-us/dnppcgen/html/build_portable_wm_apps.asp' target='_blank'>http://msdn.microsoft.com/mobility/default.aspx?pull=/library/en-us/dnppcgen/html/build_portable_wm_apps.asp</a><br /><br /></div><i>"An assumption underlying Microsoft's Windows Mobile development tools is that developers want to target one specific platform (for example, either Pocket PC or Smartphone — but not both). For developers who target multiple platforms, one solution is to ship a different set of executables for each platform. With just a bit more effort, however, a developer can build a single set of executables to support multiple platforms. This article discusses steps that you can take toward building a single executable — or set of executables — to target multiple Windows Mobile–based platforms. Although Microsoft development tools are often geared toward single-platform targeting, Microsoft, as a company, tends to prefer a more integrated approach. In other words, the company's products suggest an approach that minimizes redundancy. Some people refer to this approach as "über-integration.""</i><br /><br /><img src="http://www.smartphonethoughts.com/images/msdn_masthead_ltr.gif" alt="User submitted image" title="User submitted image"/><br /><br />Even though the Pocket PCs and Smartphones have different hardware form-factor and UI layout, the programming interface for both are identical. Mobile application developers can leverage the unified programming interface to keep their development costs down. Paul Yao has written a helpful article detailing the steps that the developers need to take to write a single application that can run on both the devices. :)