Introduction to Development Tools for Windows Mobile based Pocket PCs and Smartphones. July 2003 Microsoft Corporation

Transcription

1 Introduction to Development Tools for Windows Mobile based Pocket PCs and Smartphones July 2003 Microsoft Corporation

2 2003 Microsoft Corporation. All rights reserved. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Microsoft, ActiveSync, ActiveX, Authenticode, MSDN, SQL Server, Visual Basic, Visual C++, Visual Studio, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Development Tools for Mobile Applications 1

3 INTRODUCTION Since launching the Microsoft Windows CE operating system in 1996 and the Handheld PC version 1.0 product shortly thereafter, Microsoft has helped developers target Windows Mobile -based platforms with a selection of powerful and increasingly specialized tools that address specific needs and application tasks. Currently, Microsoft offers different tool packages for building applications for Windows Mobile-based Pocket PCs and Smartphones. This white paper provides developers with an understanding of the current and future landscape of Windows Mobile application development tools. It helps them decide which offerings are most suitable for specific needs, when to use each tool, and what mobile application developers need to get started on their mobile application projects. The paper also provides information comparing the merits of specific tools. While the current choice of mobile development tools consists of an assortment of offerings and will continue to be enhanced, Microsoft s goal is to eventually create a unified development environment to meet all mobile application development needs, which includes integrating mobile development tools into the core Microsoft Visual Studio.NET product offering. Development Tools for Mobile Applications 2

4 TOOLS FOR MOBILE APPLICATION DEVELOPMENT The following sections provide an overview of the tools currently available for Windows Mobilebased Pocket PCs and Smartphones. When reading the descriptions of the tools, developers should consider them in the context of using native, managed or server-side code: Use native code for high performance, if you need direct hardware access or if you require a small footprint. Use managed code for user interface-centric applications that require fast time-to-market or rapid application development. Also use managed code if you want easy access to web services. Use server-side code for targeting a wide variety of devices with a single code set and where there is guaranteed data bandwidth to the device. The embedded Visual Tools 3.0 Microsoft embedded Visual Tools 3.0 provide an entry-level integrated development environment for building mobile applications, including necessary compilers, debugging and platform documentation. The embedded Visual Tools 3.0 include Microsoft embedded Visual C (evc 3.0) and embedded Visual Basic 3.0 (evb 3.0). Both tools are separate development environments and do not require any other development environment, such as Microsoft Visual Studio or Visual Studio.NET, to run. To target a Windows Mobile-based device, all tools require a platform Software Development Kit (SDK) for the device you want to target. The 2002 edition of the embedded Visual Tools 3.0 includes the SDKs for all current Windows Mobile devices, including Pocket PC 2002 and Smartphone SDKs for devices outside the Windows Mobile family of devices should be available from the device manufacturer. You can download the embedded Visual Tools edition for free at More information about embedded Visual Tools is available at embedded Visual C The Microsoft embedded Visual C development system offers the native code C++ compiler for Windows Mobile-based development. It can target all devices based on Windows CE 2.11 and 3.0 if the correct SDK is installed. The embedded Visual C++ debugger works via Microsoft ActiveSync through a wired, wireless LAN or cradle connection. There are software emulators available for Pocket PC 2002 and Smartphone 2002 devices. When Pocket PC 2002 was released, Microsoft introduced a new emulator for the Pocket PC 2002 SDK that is closer to a real Windows Mobile-based device. The new emulator runs true Windows CE binaries in a virtual PC shell. The Smartphone 2002 and Pocket PC 2003 SDKs also use this new emulator. Use embedded Visual C++ for: Drivers for the Pocket PC or any other Windows Mobile-based device Development Tools for Mobile Applications 3

5 Applications that run natively on the device Games using high-speed graphics through the Game API (GAPI) Applications with intense processing requirements COM servers or Microsoft ActiveX controls embedded Visual Basic 3.0 embedded Visual Basic 3.0 enables applications that use the Visual Basic language; the resulting P-code is interpreted at runtime. While most Windows Mobile-based devices have built-in capabilities to run applications built with embedded Visual Basic, some custom embedded Windows CE-based hardware platforms may not contain the embedded Visual Basic runtime. Windows Mobile 2003 software for Pocket PC does not contain the Visual Basic runtimes, however, they are available for download from embedded Visual Basic is based on a scripting language rather than on the full-featured Visual Basic language. Therefore, many language features available in Visual Basic 6.0 for the desktop are not supported in embedded Visual Basic 3.0. For example: All variables are variant by default; strong typing is not supported ActiveX controls cannot be developed with embedded Visual Basic, but they can be hosted Several Visual Basic intrinsic controls are not supported and some properties are missing embedded Visual Basic cannot be used to develop applications for Windows Mobile 2002-based Smartphone. Due to this and other factors, including the strong interest in the development community in Visual Basic.NET, the embedded Visual Basic technology is being phased out and replaced by the more powerful Visual Basic.NET language. Microsoft recommends that developers use Visual Basic.NET to create all new Pocket PC applications and use embedded Visual Basic for maintaining older applications. embedded Visual C Microsoft embedded Visual C supports development for the new Windows CE.NET 4.2 based devices and, via a service pack release, supports Windows Mobile 2003 software for Pocket PCs (formerly code-named Ozone ). embedded Visual C is ideal for targeting mobile or embedded devices based on Windows CE.NET 4.2 using native code. Enhancements of embedded Visual C include: Just-In-Time debugging for diagnosing unhandled exceptions C++ structured exception handling Attach-to a process for improved process debugging Better integration with the new emulator You can download embedded Visual C++ 4.0, evc 4.0 Service Pack 2 and the SDK for Windows Mobile 2003 software for Pocket PC from Smart Device Programmability Features of Visual Studio.NET 2003 The Smart Device Programmability (SDP) features of Visual Studio.NET, formerly known as the Smart Device Extensions (SDE), help developers write mobile applications that take advantage of the Microsoft.NET Compact Framework, enabling distributed mobile computing in either connected or disconnected scenarios. The extensive class library available through the.net Compact Framework allows applications to be written much faster than with traditional tools. Development Tools for Mobile Applications 4

6 Visual Studio.NET 2003 enables Pocket PC 2002 and, with the appropriate SDK, Pocket PC 2003 development using the same tools and techniques as desktop development. It installs the.net Compact Framework, which is specifically designed for resource-constrained devices. Developers can use the new C# language or the Visual Basic.NET language to target mobile and embedded devices. It also works well for applications that use XML Web services, and leverages ADO.NET. Use Visual Studio.NET 2003 for: Applications that take advantage of Web services Applications that must work well in either a connected or disconnected environment Developing applications using either Visual Basic.NET or C# When you wish to use the same tools for desktop, server and device programming Rapidly developed mobile applications Software that provides a reliable and secure environment Applications that may be moved to different devices with different CPUs or a variety of Windows versions For more information on the Smart Device Programmability features of Visual Studio.NET, go to ASP.NET Mobile Controls ASP.NET Mobile Controls, formerly known as the Microsoft Mobile Internet Toolkit (MMIT), complement Smart Device Programmability and the.net Compact Framework. ASP.NET Mobile Controls extend the power of the.net Compact Framework and Visual Studio.NET for building mobile Web applications by enabling ASP.NET to deliver markup to a wide variety of mobile devices. With this approach, developers can use Visual Studio.NET to build a single mobile Web application that automatically adapts its page rendering for a wide variety of devices, such as Internet-enabled cell phones, pagers and PDAs, like the Pocket PC. It also eases development tasks because it integrates into the Visual Studio.NET Integrated Design Environment (IDE), allowing developers to build mobile Web applications by dragging and dropping controls onto a mobile Web form. ASP.NET does not install any components on the client device. Instead, it uses server-side logic to adapt the rendering to a specific device s Web browser. It generates Wireless Markup Language (WML), HTML and compact HTML (chtml). In addition to adaptive Web page rendering, ASP.NET offers a rich framework for customization and extensibility, providing an easy means of extending the controls to take advantage of new and different devices that will enter the market. Additionally, ASP.NET lets developers control the rendering for a specific device or class of devices within the same programming model, and allows developers to easily add support for new devices without re-authoring their mobile Web applications. Use ASP.NET Mobile Controls for: Supporting a wide range of Web-enabled devices (cell phone, pagers, PDAs) Supporting different markup languages (WML, chtml, HTML) Note: ASP.NET Mobile Controls do not require any client-side installation however the target device must have a client Web browser. For more information about Microsoft ASP.NET Mobile Controls, go to Development Tools for Mobile Applications 5

7 Microsoft SQL Server 2000 Windows CE Edition Version 2.0 Microsoft SQL Server 2000 Windows CE Edition (SQL Server CE) version 2.0 is the compact database for rapidly developing applications that extend enterprise data management capabilities to mobile devices. SQL Server CE is a powerful tool that makes it easy to develop mobile applications by supporting familiar Structured Query Language (SQL) syntax and providing a development model and API consistent with SQL Server. The SQL Server CE engine exposes an essential set of relational database features, such as an optimizing query processor and support for transactions and assorted data types, while maintaining a compact footprint that preserves precious system resources. Remote data access and merge replication ensure that data from SQL Server databases is delivered reliably; can be manipulated offline; and can be synchronized later to the server, making SQL Server CE ideal for mobile and wireless environments. SQL Server CE 2.0 is designed to integrate with the.net Compact Framework through Visual Studio.NET, simplifying database application development for smart devices. Using the new SQL Server CE data provider to manage code by means of the Common Language Runtime, mobile application developers can build highly extensible applications with offline data management capability for disconnected scenarios. Use SQL Server CE as a complement to your development tools when: Extending enterprise data management capabilities to Pocket PCs Developing applications that store and manipulate significant amounts of data on a mobile device Needing reliable data replication with mobile devices in environments with intermittent connectivity For more information about SQL Server CE, go to Development Tools for Mobile Applications 6

8 The Tools Comparison Chart The following chart provides an overview of the capabilities of the different tools. embedded Visual Tools edition embedded Visual C Visual Studio.NET 2003 embedded Visual C embedded Visual Basic 3.0 embedded Visual C (SP2) Smart Device Programmability (.NET Compact Framework) ASP.NET (as part of VS.NET) Code type Native Code x x Interpreted Code x Managed Code x Server- side code x Device SDKs Pocket PC or Pocket PC 2002 x x x x Smartphone 2002 Pocket PC 2003 Key : x Supported x x x x x Development Tools for Mobile Applications 7

9 Development Scenarios In the short term, the most common tools for developing for Windows Mobile-based devices are the embedded Visual Tools 3.0 for Pocket PC 2000 and 2002, embedded Visual C for Smartphone 2002 and embedded Visual C for Pocket PC Eventually, Visual Studio.NET with its Smart Device Programmability (SDP) features will be the development platform for all Windows Mobile-based devices. Server-side or Client-side Code? The decision to use server-side or client-side code depends on several criteria. Each application scenario is different; however, these criteria should help you select the best solution for the users of your application. User experience: Client applications generally provide better user experience as they run locally on the device and are independent of any infrastructure with which they interact. Available bandwidth: This relates to user experience. An application running in an environment where there is significant and reliable bandwidth, such as a wireless LAN, can provide a good server-side code user experience. Data security: A client application must secure sensitive data on the device. Windows Mobile software provides a number of Cryptographic Service Providers that assist with this. Server side applications must ensure that data is transmitted securely using technologies like SSL. Supportability: Updates to a client application must be downloaded and installed to the device. Consider this scenario when thinking about a client application. Offline functionality: If offline data access and functionality is required, a client-side application is best. What Do You Need to Develop for Windows Mobile-based Pocket PC and Smartphone? What you need to develop for Pocket PC and Smartphone depends on what you are trying to develop and which device you are targeting. In most cases you will need to have an integrated development environment and an SDK or extension for the device you want to target. The good news is that you can write applications to target the complete range of Windows Mobile-based devices from one machine as all the tools will co-exist. See the appendix for our recommended installation order. Currently the embedded Visual Tools IDE and necessary SDKs are free and available for download over the Web. Which Tool When? I want to target Smartphone 2002 You should download the embedded Visual Tools Edition, which contains the development environment, emulator and SDK to target this family of devices from If you want to test your application on a real device but Smartphone is not yet available in your territory or does not support development, you can buy a Smartphone Developer Kit. For more information check out Development Tools for Mobile Applications 8

10 Performance, control or footprint are important to me, for example I want to write a game, device driver or an Active X component If you plan to target only the newer Pocket PCs running Windows Mobile 2003 software, for Pocket PC 2003 you only need to download embedded Visual C++ 4.0, Service Pack 2 and the Pocket PC 2003 SDK from To support earlier Pocket PC, Pocket PC 2002 and Smartphone 2002 devices you would also need to download the embedded Visual Tools Edition, see If you need to maintain applications targeting the Handheld PC Professional Edition, Handheld PC 2000 or Palm Size PC 1.2, you can download the SDKs for embedded Visual Tools 3.0 through AAC5-0AFFD5FB27DD&displaylang=en. I want to develop an application quickly in a secure and reliable environment, I might want to access web services I want to write a client application that has maximum code portability I want to use my Visual Studio.NET 2003, Visual C#, Visual Basic.Net or.net Framework skills We recommend you use the Smart Device Programmability features in Visual Studio.NET The.NET Compact Framework is built into Windows Mobile 2003-based Pocket PCs. It is available for Pocket PC 2002 although must be installed to the device. I want to maintain an application written in embedded Visual Basic You should download the embedded Visual Tools Edition, which contains the development environment, emulator and SDK for embedded Visual Basic Consider porting your application to the.net Compact Framework using Visual Basic.NET I want to write an application that targets a wide variety of mobile devices that can operate in a thin-client environment You should use ASP.Net Mobile controls as part of Visual Studio.NET You can find more information at Development Tools for Mobile Applications 9

11 CONCLUSION Microsoft is committed to the long-term success of the mobile device market and to helping developers deliver rich, highly functional mobile applications for enterprise users and consumers. The Windows-based mobile application development languages currently available provide an incredible range of power and flexibility. As new generations of mobile devices appear on the market, Microsoft will continue delivering increasingly sophisticated and unified development tools that enable developers to rapidly design and deliver new applications that take advantage of technologies such as Web services and systems that exploit the power of.net-based integration. The availability of these tools will give the mobile application development community the tools it needs to continually provide rapidly growing markets with the applications they need. Development Tools for Mobile Applications 10

12 Appendix : Recommended Installation Order for Development Tools for Mobile Applications In order to ensure the maximum interoperability between the different tools for developing for Windows Mobile software, we recommend you install the tools and SDKs in the following order. If you do not have or do not need one of the tools you need not obtain it in order for the other tools to interoperate, The following installation steps require you to be logged onto to your computer using an account with Local Administrator privileges. 1. Uninstall all existing tools, SDKs and Emulators Before Proceeding You should uninstall the following programs before proceeding with this installation: o embedded Visual Tools 3.0 o embedded Visual C o embedded Visual C Service Pack 2 o Visual Studio.NET 2003 o Pocket PC 2003 SDK o Pocket PC 2002 SDK o Smartphone 2002 SDK o Pocket PC 2000 SDK o Standard SDK for Windows CE.Net o Microsoft ActiveSync 2. Install Microsoft ActiveSync 3.7 All the Development Tools for Mobile Applications require ActiveSync 3.7 for application development and deployment. If you do not have ActiveSync 3.7, you can obtain it from 3. Install the embedded Visual Tools 2002 Edition, Pocket PC 2002 SDK and Smartphone 2002 SDK In order to develop C++ and Visual Basic applications for the Pocket PC and Smartphone 2002 platforms you must install the embedded Visual Tools 2002 edition. You can download the setup package from Note, the setup for the embedded Visual Tools 2002 Edition will also start the installation process for the Pocket PC 2002 and Smartphone 2002 SDKs. 4. Install embedded Visual C and Service Pack 2 In order to develop C++ applications for the Pocket PC 2003, you must install Microsoft embedded Visual C and Service Pack 2. You can download them from tp://msdn.microsoft.com/vstudio/device/embedded/download.asp. Note that you can install Service Pack 2 only after embedded Visual C is installed. Note, installing embedded Visual C Service Pack 2 on Windows Server 2003 may cause a pop-dialog box to come up and prompt that one of the emulator drivers is not signed. You should accept the unsigned driver and continue. Development Tools for Mobile Applications 11

13 5. Install Visual Studio.NET 2003 In order to develop applications in C# or Visual Basic.NET for Pocket PC 2002, Smartphone 2002 or Pocket PC 2003, you must install Visual Studio.NET Pocket PC 2003 devices and the Pocket PC 2003 Emulation images already contain the.net Compact Framework. You must deploy the.net Compact Framework on earlier devices. 6. Install the Pocket PC 2003 SDK To develop applications in C++, C# or Visual Basic.NET for Pocket PC 2003 you must install the Pocket PC 2003 SDK. You can download this SDK from Development Tools for Mobile Applications 12