Windows Mobile Application Development | DigRecent

Sun	Mon	Tue	Wed	Thu	Fri	Sat
	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28

Mobile and compact devices are increasingly common in our society. Each of us must face every day. Of course, we all have mobile phones, handheld computers or other devices Hi Tech. All these devices have several mobile platforms. Are known as platforms such as Windows MobileMe, iPhone, BlackBerry, Symbian OS, Android, Maemo, OpenMoko, etc. All have different backgrounds and the advantages and limitations. Presentation of platforms like Windows Mobile, BlackBerry, iPhone is “closed” and is a bit ‘limited by their own means (BlackBerry, iPhone) or the complexity of development. Other problems platforms above, is restricted API. Even the Java platform for mobile devices has some defects, such as number of limitations, the API is very different device dependent code. Symbian and Windows Mobile are better from this point as the support of a wide range of devices and their API to give more options. Common problem is that there is a lot of platforms. Speaking of open source and cross-platform, it seems that they are still developing at the moment and are not yet widespread. In this article, we will pay our attention to the Windows Mobile platform. Microsoft has released its first enterprise platform for embedded devices, at the end of 90. In 2002, Windows CE. NET appeared. Now Pocket PC based on Windows CE 3. 0 Platform and higher have been issued. The development of wireless communication technologies has managed to combine phone and personal computer. So, Pocket PC 2002 Phone Edition appeared that supported the standards of GSM, GPRS, Bluetooth and HS wireless network access. Meanwhile, another device concept was developing that was very similar to that described above, but it was closer to the phone and personal computer. This device is called Smartphone 2002. Fundamental difference between the smartphone and Pocket PC and Pocket PC with a touchscreen smartphone has all the control buttons. Had also extended to different application and supporting various standards and technologies. Platform Windows Mobile for Smartphone is more, communicators and small personal devices. Windows CE and Windows Embedded platforms are commonly used in various industrial plants. Now we have Windows Mobile 5 and Windows Mobile 6 generations and Windows Mobile 7 will be available soon. Modern devices based on Windows Mobile Pocket PC is 64-128 MHz and 500-600 MB of RAM that is not unusual for these devices. 1. Development tools are few models for developing applications for Windows Mobile: Win32 API MFC. NET Compact Framework. Co Microsoft offers developers all the tools needed to develop applications for PDA, Pocket PC and Smartphone. Here are some tips about choosing the type of code. Using native code for performance failure, working directly with the material, and also to minimize the requirements of system resources. Using managed code to develop GUI applications based on which the main requirements are to develop and how to penetrate the market. Managed code is also good for the job easy with web services. Using server-side code to work with different devices using a single code base, and the channel of communication even in a comprehensive way, with a permanent mechanism is present. Here are reviews of development tools present for PDA, Pocket PC and Smartphone. eMbedded Visual C + + 4. 0 Microsoft eMbedded Visual C + + 4. 0 development environment designed to create applications for devices running Windows CE. NET 4. 2 operating system and also (with the update package, SP3) for PDA and Smartphones with Windows Mobile 2003 Second Edition. The development environment embedded Visual C + + 4. 0 is good for creating native code built for mobile devices with Windows CE. NET 4. 2 OS. It allows developers to perform Just-In-Time Debugging for diagnosing unhandled exceptions, connect to the process of debugging processes extended, and also the interaction with an emulator. Visual Studio. NET and functions SDP SDP (Smart Device Programming) functions of the IDE of Visual Studio. NET 2003 (2005, 2008) you can create applications that use the possibilities of Microsoft. NET Compact Framework platform. Thus, a developer can create mobile data distributed processing systems, the sites in both scenarios with and without connection persistent connection. Extensive class library. NET Compact Framework platform allows development of applications much faster than traditional development tools. Visual Studio. NET to create applications for Pocket PC 2002 and (with the development kit clean) Pocket PC 2003, 2005 and Smartphone 2003, 2005, using the same tools used for developing applications for desktop PCs. Library. NET Compact Framework is installed with Visual Studio. NET. This library has been developed specifically for devices with limited resources. Developers can also use new languages C # and Visual Basic. NET applications for mobile devices and integrated. They are good at building web sites with services and ADO. NET technologies. The control of the ASP. NET mobile controls and extend the capabilities of SDP. NET Compact Framework platform. Give the possibility to use the opportunities offered. NET Compact Framework and Visual Studio. NET for developing Web applications for mobile delivery of data on different mobile devices using ASP. NET technologies. This approach allows to create mobile Web applications in Visual Studio simple. NET, which automatically records the data for display on different devices: mobile phones, smartphones, PDAs, Pocket PC. The integrated development environment for creating mobile Web applications by simply dragging the control elements on the forms. ASP. NET does not fix the system components on a client machine. For an adaptation of formatting in the browser server concrete logic is used. Generates information in formats Wireless Markup Language (WML), HTML and Compact HTML (cHTML). Microsoft SQL Server Microsoft SQL Server Compact Edition (SQL Server CE) is a DBMS Pact for the rapid development of applications that extend the possibilities of working with data from the company because of the use of mobile devices. SQL Server CE is a tool to facilitate the development of mobile applications with support of SQL syntax and use of the application model and API, which is compatible with SQL Server. SQL Server CE provides the basic set of functions of relational databases, particularly optimized query manager, support for transactions and types of heterogeneous data – Requirements without contention for system resources. Remote access to data and the confluence of replication to ensure the delivery of reliable information database of SQL Server, you can work independently, with information and synchronize with the server later. SQL Server CE is good for systems with mobile devices and wireless networks. SQL Server CE database system was developed for integration with. NET Compact Framework using Visual Studio. NET. Simplifies development of applications for working with databases and mobile devices constructed. New data provider for SQL Server CE to run the code in the common language runtime, you can develop applications distensible with them the employment opportunities of the information in the scenarios without continuous connection. Microsoft. NET SqlClient provides APIs for the work of both. NET Framework e. NET Compact Framework. For Windows systems, the most common SqlClient with Microsoft SQL Server are used, and databases SqlServerCe for Microsoft SQL Server Compact Edition for Compact Framework. SqlClient namespace is in both versions. Thus, we are able to interact: Use. NET Compact Framework SqlClient to have access to SQL Server from a device on the desktop. Use. NET Compact Framework SqlServerCe have access to SQL Server Compact Edition directly onto a device. Working with databases on a device is similar to the desktop. To access SQL Server on the SQL Desktop system uses TCP / IP is in this case, you can not have SQL Server Compact Edition is installed on a device. All items listed are used on desktop systems. So the experience of their application can be made for the development of programs for Windows Mobile. Using the Win32 API you get the code fast, compact and can be used for the development of drivers and system components. The help of MFC, we Extensions API functions, and also the designer for the development of the interface. And the use of Compact Framework, we have at our disposal a well-developed interface, the automatic garbage collection, support for XML and other options. Also there is an even more truncated – Micro Framework, where there are fewer functions SDK. After configurations SDK for MS Visual Studio installation of new events, as well as new features for mounting on these platforms. Suit includes Emularor for developing and testing the software, without physical connection between the device and the computer. As for many devices based on Windows Mobile on ARM processors, you can also fill the unit with other compilers: AVR32, ARM (RealView), GNUARM, IAR Systems. 2. Build applications for Windows Mobile devices Windows Mobile with MS Visual Studio. NET development environment Visual Studio, and Compact Framework, you can develop applications using a graphical interface to large databases, archiving and encryption tools, USB, Bluetooth, and wireless network connections and even telephony. All these variables are provided by the SDK as well as libraries and files in the course of Platform Builder. 2. 1 User Interface Because of the presence of good design and the VS SDK, we can easily develop graphical user interface for all mobile applications and for desktop applications. The only difference is in the set of graphical components for desktop and Windows Mobile. There are also differences between the versions of the components of Smartphone and Pocket PC caused by this Pocket PC has a touchscreen and not a SmartPhone. Thus, the development of the interface smartphone is more complicated. Must be taken into account when developing software for both platforms. Here, we must also remember that the integrated software for Pocket PC will not start on the smartphone platform, while the reverse is possible – up to a particular function is called Smartphone. It is natural that many graphics and most of the functions of Full-Size picture were taken from the Windows Mobile SDK to reduce the size of the SDK on the side of the device. Only the objects were no longer needed on the left. But productivity and memory density is increasing the number of functions included in the SDK becomes larger. So the difference between the Compact Framework 1. 0 and 2. 0 is enormous. Version 1. 0 is very limited. In general, the development of graphical interfaces with frame? OMPACT it? # This is similar to that of the development of common Win32 application in C #. It is also possible to develop a GUI with the assembly of the 3D rendering engine. It is likely that GAPI (Game API), OpenGL ES (Embedded System), OpenVG (vector graphics), and other projects. While the process is rather boring to the extent that it is very important to write the code optimal because of the relatively low productivity of mobile devices. 2. 2 Communications Today, mobile devices have a wide range of communications options. Have access wireless high-speed 802. 11 Wi-Fi standard. They also use IrDA, Bluetooth and USB host / client functionality. Although the use of Irda becomes progressively less protocols and standards, Bluetooth, Wi-Fi, EDGE, GSM and USB are also often used exit. Microsoft provides these companies API ActiveSync API provides functionality to work with Sync Services, file filters, etc. Bluetooth API provides functionality for mobile and wireless devices. Connection Manager API is used to automate the login process, the management of network connections. Devices that use the Connection Manager to connect and also information on the alleged connection (eg internet). Object Exchange (OBEX) API provides functionality to work in an efficient, compact binary protocol only suitable for devices with limited possibilities. Remote API (RAPI) provides management functions and call methods on the remote side of the device. These functions are available: access to the registry, files, databases and various configurations of the device from the desktop system. The most important option is Remote Procedure Call, when we simply call the method “CeRapiInvoke ()” on the Office side to forward the name of the DLL on the device and the name of the function in this DLL and then simply call this method . Pocket Outlook Object Model API provides functions for working with objects of Pocket Outlook. It provides interfaces for synchronization and access to objects: Tasks, Calendar, Contacts. Telephony API (TAPI) comprises: extended Assisted Phone SIM Manager API API API API Short Message Service (SMS) API Telephony Service Provider (TSP) API Wireless Application Protocol (WAP) API. Mobile devices also have the opportunity to work with serial ports (USB). There are a small number of COM ports in many devices. Usually the first 3-5 of them are reserved for IrDA, Bluetooth, and other SerialPort. Other ports are available for the user. Some devices have a USB host function in other words, they are USB On-The-Go (OTG) devices that can simultaneously serve clients USB and USB Host. To this end device would need hardware and software (device drivers). The device driver is a driver that is an intermediate layer between the driver and the Host application layer. Driver gives us like “Stream Interface Driver and should contain functions such as: xxx_init XXX_Open XXX_Close XXX_Write XXX_Read XXX_IOControl Here” XXX “is replaced by” prefix “(eg” COM “,” DSK “). This keeps the code in the registry When a driver registers in the system. Detailed information about the interface device driver can be obtained from MSDN. Although a developer can use these APIs do not affect communication: Device file configuration API and application for the management of the game Home Screen API API API API API HTML Control API Shell API MIDI Speech Recognizer Vibrate API Voice Recorder Control API.. 2 3 P / Invoke Interop and Native Anywhere Compact Framework contains functions and procedures to perform basic framework, we have features like XML Serialization Security Services Interoperability Puzzle Cryptography et al. Certainly Platform Invoke calls are available. To that end – and in full context – using the functions and attributes of the System. Runtime. InteropServices and DllImport attribute to describe the functions for be called from unmanaged code. However, the functionality of these methods is limited. PtrToStructure for Class Marshal, GetComInterfaceForObject, Copy () and Read () functions, but, for example, there is no function like GetDelegateForFunctionPointer () in him . It ‘is impossible to marshal the delegate only. The function is only available GetFunctionPointerForDelegate. If we want to send a function pointer from managed code should get his FunctionPointer and only after that pass to unmanaged code for subsequent calls to it from there . So we can not send certain items, for Compact Framework can not count sizeof () for certain items. So often we only transmit the data Blitable types and arrays of this type (int, byte, char, but not bool), and transmission and reception classes and structures with IntPtr. Of course, is explained by the desire to increase performance. It is therefore recommended to use primitive types for marshaling and “class GCHandle” to save an object in the memory process and to demonstrate this memory “for unmanaged code Certainly, the performance of P / Invoke calls application C # C + + DLL is almost two times lower than the performance of method calls between C + + DLL. However, the performance of devices grows and it becomes possible to use these calls. 2. 4 Debugging MS Visual Studio allows you to debug applications on Windows Mobile yet for desktop applications. We Emulator, Microsoft Device Emulator Manager and other features such as breakpoints, wires, etc. Clocks panel, however, for debugging with native code and managed at the same time is impossible. Therefore, you can start or C + + or projects managed. It is also true for “Attach to Process. There is the possibility to attach to the process side of the device (or emulator on the side). ActiveSync is required for communication between a device and the system is installed with the SDK. An emulator can be connected to the computer via ActiveSync. Get almost complete emulation of Windows Mobile devices. Here the Smartphone and Pocket PC (or Pocket PC Phone Edition) emulators. However, a Windows Mobile device can be connected to the computer at a time yet. Debug then two devices simultaneously, for example, that interact in some way, it is quite difficult. Sure, we talk only about debugging applications developed by us, but not on applications and system services. To debug these we need the full integrated system created through the Platform Builder (in recent versions of Platform Builder is included in Visual Studio). We can also create our own SDK for Visual Studio and the Windows CE platform. An emulator can also emulate the connection with GSM and GPS support. E ‘possible to test and develop a wide range of applications, without having a physical device in their hands. Speaking of debugging with IDA, it is worth mentioning that the version 5. 1 has the ability to debug using the interactive disassembler with the use of its plugin, which is installed on a device. With options such as the distribution aspect SDK “appears in Visual Studio. Now, there are” Deploy an article in the context menu of the project, in addition to “build”, “Clean”, “Debug”. After selecting this DLL or EXE built by the current configuration is transmitted to the device. Even the column is present in the Configuration Manager, which not only “build” in some configuration option is available, but also “Deployment.” Distribution. NET projects forward not only unity but also the generations that are dependent on (dependencies). 3. Distribution and installation of applications development for Windows Mobile also requires their assembly and the creation of the installation package. To that end, this concept is that it? Abinet (. Cab), Windows Mobile. This is a common repository, but is also an installation package (MSI package sort of). E ‘assembled using Cab Wizard (exe CabWiz.) From MS VisualStudio (or command line). This utility creates “transformer load.” Cab CAB WinCEApplicationManager forward and start on a device, if the user can install the application using the instructions on the screen of the phone. E ‘can also create the setup project MSI, which includes a CAB file using Visual Studio. This package is based will be launched on the user's computer, then send? AB installation on a device to continue the installation process. E 'special Uninstall Manager on the side of the device. We must give the configuration INI-file cabinet. This INI file contains settings for managing the installation process, such as location, name of link to create a minimum OS version to install the application and other documents in the syntax. You can also include the DLL in your CAB-file to expand the installation options. This DLL contains functions such as Installer_AfterInstall “,” Installer_BeforeInstall “,” Installer_AfterUnInstall “,” Installer_BeforeUnInstall “code of these functions can be performed on the hardware side in times of a process of installation or uninstallation. When you develop the installation CAB, you can attach files, other resources, build units, add the information in the registry. They are identified as a result of the project. So there is no need to reset anything after the creation of CAB files, which will collect all the projects included and the files and put them together in an archive. 4. Security Model for Windows Mobile 5 Windows Mobile 6 and Windows Mobile-based devices for receiving, sending and analyzing information of potential value that should be protected from the insecure applications. To protect the system from unknown applications is disabled, the API access is limited and certain parts to change the registry is prohibited. The units can be marked as approved and not approved and the system uses this information to prevent unauthorized applications from starting and limit their access to the system. Access to the system via RAPI (Remote API) via ActiveSync may be limited. Certificates for safeguarding the rights of security units used for executables (EXE, DLL) files and CAB. Protecting against threats and hazards following options to help protect the equipment: protection Strict password. PIN protection. Information devices corrupt removed to prevent access to it (WM 6). Information devices on a memory card corrupted removed to prevent access to it (WM 6). Storage and Advanced Encryption Encryption Standard for SSL (WM 6).-user certificates. The identification of a device via Bluetooth can be protected (6 WM Smartphone). 2 level of implementation of the system from (monistic and dualistic access). No support for macros, so viruses can do much harm. Applications startup based on permissions. Windows Mobile devices with these models: complete applications blocked privileged privileged access to the widest. They can access any API, write in the areas Protected registration and have full access to the system. Most of the applications are the Normal template. They have no access to APIs of confidence and lack of full control. Application may not start at all if it is “locked” status. This means that is not signed by the appropriate certificate or prohibiting the user from the system suitable for alarm. The situation is similar, with Cab-files. The units run with a normal state can begin Privileged DLLs, but then work as usual. However, the unit can not run the executable inside the drive with the normal state. Written by Eugene Kordin specialist Apriori. Learn more about the development process of Apriori here.

Click Here to read more...