Windows LiveWindows Live™
 
 
José Roberto's profileJosé Roberto SiqueiraPhotosBlogListsMore Tools Help

Blog
    April 11

    Windows Mobile 6.1 Localized Emulator Images

    Fonte: http://www.pocketpcblast.com/articles/2008/4/200843-Windows-Mobile-6-12.html

     

     

     

     

     

     

     

     

     

    (view image)

    Microsoft has released the Windows Mobile 6.1 Localized Emulator Images.
    "The Windows Mobile 6.1 Emulator Images package adds emulator images to Visual Studio 2005 or Visual Studio 2008 that let you test applications for Windows Mobile 6.1. For general information about writing software for Windows Mobile, please see the Windows Mobile Developer Center. The emulator images can also be used as standalone without Visual Studio. They can be accessed through the Start Menu shortcuts.
    This package includes localized Windows Mobile 6.1 emulator images that can be used with Visual Studio to test applications or as standalone emulators without Visual Studio."

    Related Links:
    Windows Mobile 6.1 Localized Emulator Images

    8:14 AM | Add a comment | Permalink | Blog it | Mobile - Emulador
    December 13

    Skype for Windows Mobile 2.2 beta


    Skype has just released the beta version of its Windows Mobile 2.2 software, and it now supports Smartphone Edition. I was never able to get the previous version of Skype for Windows Mobile to work acceptably, but perhaps this version will be different.

    In addition to Smartphone support, the new version features an enhanced today/home screen and proxy support. It also has all the regular Skype calling features. And there are mobile device features, like being able to snap a profile pic with your phone camera and post it directly to your profile. Yea it’s obvious, but it’s still cool. I love technology.

    As I mentioned before, I’ve never been able to get mobile Skype to work, but the concept is quite appealing to me. I’m going to give this new version a try on my Blackjack tonight and see if it’s as useful as I suspect it could be. I’ll give you guys an update in the near future.

    Download Page [via jkOnTheRun]

    10:24 AM | Add a comment | Permalink | Blog it | Mobile - Emulador
    October 30

    Using Shared Variables with a PDA Emulator in LabVIEW 8.20 PDA Module

    Overview

    This document outlines the steps necessary to use network-published shared variables with a simulated PDA device, utilizing the PDA Emulator features incorporated into the LabVIEW 8.20 PDA Module. This will allow you to test applications and demonstrate the use of network-published shared variables from the development environment without having the actual PDA hardware present. The instructions within this tutorial assume you have the LabVIEW 8.20 PDA Module installed, and also require some additional tools provided by Microsoft in order to simulate a network connection between the PDA device and the host PC.

    Table of Contents

    1. Background
    2. Configuring a Virtual Network Connection
    3. Adding a PDA Emulator to the LabVIEW Project
    4. Adding Shared Variables to the Project
    5. Configuring the PDA Emulator for Shared Variables
    6. Deploying and Running the PDA Application
    7. Conclusion

    Background

    The PDA Emulators provided in the LabVIEW 8.20 PDA Module are features of the LabVIEW PDA software that allow you to emulate the hardware of various Pocket PC 2003 and Windows Mobile 5.0 devices from the development environment. The PDA Emulators open an instance of a ‘virtual’ PDA device on the development machine that emulates the Pocket PC 2003 or Windows Mobile 5.0 operating system. The example emulator shown in Figure 1 appears as a fully functional depiction of a PDA device running the Pocket PC 2003 operating system. The user can interact with and run software on the emulated device in exactly the same way they would a real portable device, which provides a useful tool for developing and debugging PDA applications without the actual PDA hardware present.


    Figure 1. Pocket PC 2003 Device Emulator

    Network-published shared variables, new to the LabVIEW 8.20 PDA Module, allow you to easily and efficiently share data between devices connected over an Ethernet or wireless network. To demonstrate the use of network-published shared variables with a PDA Emulator, some extra steps are required in order to simulate the network connection between the host PC and PDA device.

    Configuring a Virtual Network Connection


    The first step for configuring a virtual network connection between the host PC and PDA device is to establish a network connection and IP address on the host PC. If the host PC is already connected to an existing network, the PC will already have obtained an IP address, and the following procedure is not necessary. However, for systems that do not have access to a network connection or do not have a network adapter installed, it is necessary to use the Microsoft Loopback adapter to simulate a network connection on the host PC.

    Microsoft Loopback Adapter Installation
    The Microsoft Loopback adapter provides a virtual network adapter that allows you to simulate a network connection in situations where network access is unavailable. If your system has already established a connection to the network and obtained an IP address, you do not need to install the Microsoft Loopback adapter and the following steps do not apply. The Microsoft Loopback adapter is included as a component of the Windows 2000/XP operating system. The following steps describe how to install and configure the Microsoft Loopback adapter through the Windows Device Manager.
    1. Click Start, and then click Control Panel.
    2. If you are in Category view, click Switch to Classic View under Control Panel in the left pane.
    3. Double-click Add Hardware, which will bring up the Add Hardware Wizard.
    4. Click Next to begin the process of adding the Microsoft Loopback adapter as new hardware in your system.
    5. When prompted, select Yes, I have already connected the hardware, and then click Next.
    6. You will now see a list of hardware you can add to your system. At the bottom of the list, click Add a new hardware device, and then click Next.
    7. Select Install the hardware that I manually select from a list, and then click Next.
    8. From the list of hardware categories, select Network adapters, and then click Next.
    9. In the Manufacturer box, select Microsoft, and in the Network Adapter box, select Microsoft Loopback Adapter. Click Next to begin the installation process for the Microsoft Loopback adapter.
    10. Click Finish.

    The Microsoft Loopback adapter will now appear in the list of Network Adapters in the Windows Device Manager. You can check this by going to Start»Control Panel, double-click on System, select the Hardware tab, and click on Device Manager. The Microsoft Loopback adapter will automatically configure its own network connection and obtain its own IP address. You must disable any other existing network adapters in the Windows Device Manager in order for the Loopback Adapter to function properly with LabVIEW network-published shared variables. You can disable a network adapter in the Windows Device Manager by expanding the Network Adapter section, right-clicking on the entry for the existing network adapter and selecting Disable.

    Virtual PC Network Driver Installation
    Now that the host PC has a network connection and IP address, you must enable the PDA Emulator to obtain its own unique IP address so that the two can communicate to each other using network-published shared variables. The Microsoft Virtual PC Network Driver allows the PDA Emulator to simulate a network connection and obtain its own IP address. You can download the installer for the Virtual PC Network Driver from Microsoft’s website linked below. Follow the instructions on the Virtual PC Network Driver download page for installing the driver. With this utility installed, the PDA Emulator will automatically obtain its own IP address on the same subnet as your host PC and be able to communicate to your host PC using network-published shared variables.

    With these utilities installed, you have everything necessary in establish a network connection between a PDA Emulator and your host PC. The next step is to configure the PDA Emulator and network-published shared variables in the LabVIEW Project Explorer.

    See Also:
    Virtual Machine Network Driver for Microsoft Device Emulator

    Adding a PDA Emulator to the LabVIEW Project


    The LabVIEW Project Explorer provides a useful tool for managing development for various targets from a single location in the LabVIEW environment. In addition to organizing your development targets, the LabVIEW Project Explorer also contains the shared variables used to communicate between the various targets. Refer to the LabVIEW PDA Help and theCreating and Using Shared Variables in the LabVIEW 8.20 PDA Module tutorial for more information about adding PDA targets and network-published shared variables to the Project Explorer. You will begin by creating a new LabVIEW Project to organize the host PC target, PDA Emulator target, and network-published shared variables within a single location.

    Complete the following steps to create a new LabVIEW Project and add a PDA Emulator as a target to this project.
    1. From the Getting Started window, click Empty Project to open a new project. The project contains the My Computer target, which is the development, or host, PC.
    2. Select File»Save As in the Project Explorer window and save the new project as PDA Emulator Shared Variable.lvproj.
    3. Right-click the project and select New»Targets and Devices from the shortcut menu to open the Add Targets and Devices dialog box.

    4. Select Existing target or device and expand the PDA category to show the available targets. Rather than selecting an actual PDA device, select PDA»Windows Mobile»Pocket PC 2003 SE Emulator to add a Pocket PC Emulator target to the project.


    The Pocket PC 2003 SE Emulator now appears as a new target within the project.

     


    Adding Shared Variables to the Project

    You can now add network-published shared variables to the LabVIEW project. The shared variables provide a memory space that can be used to send and receive data between different targets in the project. One target in the project must host the shared variables. All other targets can connect to that host as clients to publish or subscribe to the data stored in the shared variable memory space. Only certain targets, such as Windows PCs, FieldPoint controllers, and CompactRIO controllers are capable of hosting shared variables. PDA targets and emulators cannot host shared variables and can only access shared variables as clients. You create and host the shared variables on the host PC. The PDA target serves as a client and subscribes/publishes to the shared variables remotely that are hosted on the host PC.

    Complete the following steps to add shared variables to the project.

    1. Right-click My Computer in the Project Explorer window and select New»Variable from the shortcut menu to open the Shared Variable Properties dialog box.


    2. Give the shared variable a logical name by typing Temperature in the Name text box.
    3. Select Double from the Data Type drop-down list.
    4. Select Network Published from the Variable Type drop-down list.


      [+] Enlarge Image
    5. Click the OK button.The shared variables appear in the Project Explorer window under Untitled Library 1. LabVIEW automatically creates this library because all shared variables must reside in a library in a project.
    6. Right-click Untitled Library 1, select Save As from the shortcut menu, and save the library as Weather Data.lvlib.
    Create another network-published shared variable and name it Wind Speed.



    Complete the following steps to add Weather Station.vi to the My Computer target, and PDA Weather Monitor.vi to the PDA Emulator target. These files are attached at the end of this tutorial. For step-by-step instructions of how these VIs were created, refer to the Creating and Using Shared Variables in the LabVIEW 8.20 PDA Module tutorial.
    1. Right-click the My Computer target and select Add File. Browse to Weather Station.vi and select Add File to add this VI as a program under My Computer. This VI simulates weather data and publishes that data to the network-published shared variables.
    2. Right-click the Pocket PC 2003 SE Emulator target and select Add File. Browse to PDA Weather Monitor.vi and select Add File to add this VI as a program under the PDA Emulator target. This PDA VI subscribes to the network-published shared variables hosted on My Computer and displays the data on the user interface of the PDA Emulator.

    The Project Explorer should now look similar to the following.

    You will now need to create a Build Specification for the PDA Weather Monitor.vi, in order to compile the PDA VI into an executable for the Pocket PC 2003 OS.
    1. Under the Pocket PC 2003 SE Emulator, right-click Build Specifications and select New»Application (EXE).
    2. In the Application Information section, enter PDA Weather Monitor for the Build specification name and a convenient location on disk for the Destination directory (i.e. <My Documents>\PDA Weather Monitor). You will need to know this location later in order to transfer the executable to the PDA Emulator.
    3. In the Source Files section, add PDA Weather Monitor.vi as the Top-Level VI.
    4. In the Machine Aliases section, select Deploy aliases file. The aliases file contains the IP addresses of the targets in your project and allows them to communicate through network-published shared variables.
    5. Click OK in order to complete the build specification settings.
    6. To compile the PDA Weather Monitor.vi into an executable, right-click the PDA Weather Monitor build specification and select Build.


    The PDA Weather Monitor.vi has now been compiled into an executable to run on the Pocket PC 2003 OS. You are now ready to launch an instance of the Pocket PC 2003 Emulator and deploy this executable.

    See Also:
    Tutorial: Creating and Using Shared Variables in the LabVIEW 8.20 PDA Module

    Configuring the PDA Emulator for Shared Variables


    The next step is to launch an instance of the Pocket PC 2003 Emulator and configure it to support shared variables.
    1. Within the LabVIEW Project Explorer, right-click on the Pocket PC 2003 SE Emulator target and select Install»Support for Shared Variables.


    This will launch an instance of the Pocket PC 2003 Emulator and install the necessary files to support connections to network-published shared variables. This process may take several seconds, and you will know this is complete when the PDA Emulator shows the following PDA desktop.

    The next step is to deploy the PDA Weather Monitor executable to the PDA Emulator target. When working with actual PDA hardware, this deployment process occurs automatically when the PDA device is connected to the development PC through Microsoft ActiveSync. For an emulated PDA target, you can use folder sharing to transfer the PDA executable to the PDA Emulator. Complete the following steps to configure folder sharing between the PDA Emulator and the development PC.
    1. From the Pocket PC 2003 SE PDA Emulator, select File»Configure to open the Emulator Properties dialog box.
    2. In the Shared folder field, enter the same path you selected for the Destination directory when creating the PDA Weather Monitor build specification. This will allow you to access the contents of that directory, including the compiled PDA Weather Monitor executable, from the File Explorer on the PDA Emulator.


      [+] Enlarge Image

     

    Deploying and Running the PDA Application

    With the PDA Weather Monitor.vi compiled into a Pocket PC 2003 executable, you are now ready to deploy and run the executable on the PDA Emulator and connect to an application running on the host PC through network-published shared variables. With folder sharing enabled on the PDA Emulator, you can use File Explorer on the PDA Emulator to deploy and run the PDA Weather Monitor executable.
    1. To launch File Explorer, from the PDA Emulator desktop, select Start »Programs. Select File Explorer from the list of programs.



      The shared folder containing the PDA Weather Monitor executable will appear as an external Storage Card on the PDA Emulator.
    2. To browse to the shared folder from File Explorer on the PDA Emulator, select My Device from the Show drop down list.


    3. To access the contents of the shared folder, select Storage Card.


    4. To launch the executable on the PDA Emulator, click PDA Weather Monitor.exe. Clicking the Run button on the front panel will start the application, but first you must deploy and publish data to the network-published shared variables.
    With the PDA Weather Monitor application deployed to the PDA Emulator, you will need to run the Weather Station.vi application on the host PC. Running this application will automatically deploy the Temperature and Wind Speed network-published shared variables on the host PC, and begin publishing simulated weather data to these shared variables. With the shared variables deployed and data being published, you can run the PDA Weather Monitor executable on the PDA Emulator in order to subscribe to those shared variables over the network and present the data on the user interface of the PDA.
    1. From the LabVIEW Project Explorer, double-click to open Weather Station.vi, and click the Run button. This will deploy the Temperature and Wind Speed shared variables, and begin publishing simulated data.
    2. From the PDA Emulator, click the Run button on the user interface of the PDA Weather Monitor application to subscribe and display the data from the Temperature and Wind Speed shared variables.

    Conclusion

    To review the steps covered in this tutorial, you first began by configuring the host PC and PDA Emulator target to connect to each other over a local network connection. You then created a PDA Emulator target within the LabVIEW Project Explorer and added network-published shared variables and VIs to the project. You then compiled the PDA VI into an executable by creating a build specification, and deployed that executable to the PDA Emulator through folder sharing. With these steps complete, you can run applications on the host PC and PDA Emulator target that communicate to each other using network-published shared variables. This procedure can be very useful for demonstrating the use of shared variables with PDA target and testing applications without the actual PDA hardware present.
    0 ratings | 0.00 out of 5
    | Print Document | Open document as PDF

    Reader Comments | Submit a comment »

     

    Legal
    This tutorial (this "tutorial") was developed by National Instruments ("NI"). Although technical support of this tutorial may be made available by National Instruments, the content in this tutorial may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this content with each new revision of related products and drivers. THIS TUTORIAL IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).

    8:52 PM | Add a comment | Permalink | Blog it | Mobile - Emulador
    September 29

    Using the Windows Mobile 5.0 Emulators in Visual Studio 2005

    Windows DevCenter    
     Published on Windows DevCenter (http://www.windowsdevcenter.com/)
     http://www.windowsdevcenter.com/pub/a/windows/2006/01/24/windows-mobile5-emulators-in-visual-studio-2005.html

     See this if you're having trouble printing code examples

    Using the Windows Mobile 5.0 Emulators in Visual Studio 2005

    by Wei-Meng Lee
    01/24/2006

    If you have ever developed mobile applications, you know the importance of using emulators. Emulators allow you to test your application on different types of target platforms without needing to buy all these devices (which is not practical, as it is almost impossible to test your application on all makes and models). And so the emulator plays a very important part in the development cycle: How realistically can it emulate a real device? Are you able to drag and drop files onto the emulator? Can you install applications onto the emulator?

    In this article, I will explore the emulator tools support that shipped with Windows Mobile 5.0 and Visual Studio 2005, and how you can use them to help in your mobile application development.

    What You Need

    For this article, you will need the following:

    • Visual Studio 2005 (Final Release).
    • ActiveSync 4.1. ActiveSync is used to synchronize your computer and your Windows Mobile devices (Pocket PC and Smartphone). I'll show you how you can synchronize your emulator with ActiveSync.
    • Windows Mobile 5.0 SDK. Visual Studio 2005 ships with only the Pocket PC 2003 and Smartphone 2003 emulators. If you are targeting Windows Mobile 5.0 devices, you need to download the following SDKs:

    Creating a Windows Mobile 5.0 Application

    Let's first start by using Visual Studio 2005 to create a Window Mobile 5.0 Pocket PC application. In Visual Studio 2005, go to File-->New Project, then select the Windows Mobile 5.0 Pocket PC project type and choose the Device Application template. Use the default name of DeviceApplication1 and click OK (see Figure 1).

    Figure 1
    Figure 1. Creating a new Windows Mobile 5.0 Pocket PC application

    Deploying to an Emulator

    Once the project is created, you will see a default Windows Forms. We are not really interested in populating this form; what we are interested in is deploying it onto an emulator. Press F5 to debug the application. You will be asked to select a device to deploy your application (see Figure 2).

    Figure 2
    Figure 2. Choosing the device to deploy to

    Select Windows Mobile 5.0 Pocket PC Emulator and click Deploy. The emulator will be launched and then a while later the application is deployed onto it (see Figure 3).

    Note: If you are deploying a Windows Mobile application onto an emulator for the first time, it may take a while for the application to load. This is because Visual Studio 2005 is busy installing the .NET Compact Framework 2.0 class libraries onto the device. Subsequent deployment will be much faster. For your information, Windows Mobile 5.0 devices do not ship with .NET Compact Framework 2.0; they come with .NET Compact Framework 1.0 in ROM.

    Figure 3
    Figure 3. The emulator and the deployed application

    Connecting to Different Emulators

    In the last section, you saw how you can launch an emulator when you deploy an application. However, this is not always necessary. In Visual Studio 2005, there is now a Device Emulator Manager, which you'll find at Tools-->Device Emulator Manager (see Figure 4).

    Figure 4
    Figure 4. The Device Emulator Manager

    In the Device Emulator Manager, you can right-click on the emulator that you want to launch and select Connect (see Figure 5). The selected emulator then is launched.

    Figure 5
    Figure 5. Selecting an emulator to launch

    Connecting an Emulator to ActiveSync

    While you can launch an emulator and try out all the various features available in the platform, a much more useful feature is the ability to connect to the outside world. You may want to install a third-party application onto the emulator and see how it runs, or you may just need to transfer some files into and out of the emulator, onto your PC.

    To do so, you need to use ActiveSync to connect to the emulator. First, in ActiveSync, go to File-->Connection Settings, and in the options for Allow Connections to One of the Following, select DMA (see Figure 6).

    Figure 6
    Figure 6. Configuring the connection settings in ActiveSync

    Next, in the Device Emulator Manager, right-click on the emulator that is currently running and select Cradle. Once this is done, you will notice that ActiveSync now detects a connection from the emulator. The Synchronization Setup Wizard will now appear (see Figure 7). Click Next to proceed.

    Figure 7
    Figure 7. The ActiveSync Synchronization Wizard

    As usual, you can configure your synchronization options (see Figure 8). Click Next and then Finish.

    Figure 8
    Figure 8. Configuring the synchronization options



    ActiveSync should now be connected with your device (see Figure 9).

    Figure 9
    Figure 9. ActiveSync connected to the emulator

    Once the emulator is connected to ActiveSync, you can explore the file system on the emulator by clicking the Explore button in ActiveSync. Figure 10 shows the location of the application (\Program Files\DeviceApplication1\DeviceApplication1.exe) that was deployed earlier.

    Figure 10
    Figure 10. Locating the application that was deployed earlier

    Besides exploring the emulator's file system, you can now also install applications onto your emulator. You can now directly install Pocket PC applications onto your emulator (see Figure 11) through ActiveSync.

    Figure 11
    Figure 11. Installing an application onto the emulator through ActiveSync

    Within minutes, I am having fun with some games on the emulator (see Figure 12). This ability to install applications onto the emulator is useful when you are building installation packages for your Windows Mobile 5.0 applications and you want to test them out without using a real device.

    Figure 12
    Figure 12. Playing games on the emulator



    Changing Screen Orientation

    Beginning with Windows Mobile 2003 Second Edition, all devices support both the landscape and portrait screen orientations. As a Windows Mobile developer, it is your duty to ensure that your application is orientation-aware, and hence testing your application in both orientations is important.

    In Start-->Settings (on the emulator; see Figure 13), select the System tab and the Screen item.

    Figure 13
    Figure 13. Launching the Screen application on the emulator

    Select the Landscape orientation option (see Figure 14) and click OK. The emulator will be rotated according to the option selected.

    Figure 14
    Figure 14. Changing screen orientation

    Visual Studio Remote Tools

    Visual Studio 2005 ships with a set of tools for Windows Mobile developers. You can find the tools by going to: Start-->Programs-->Microsoft Visual Studio 2005-->Visual Studio Remote Tools (see Figure 15).

    Figure 15
    Figure 15. Remote tools in Visual Studio 2005

    Remote File Viewer

    The Remote File Viewer works similar to the Windows Explorer with which you are probably familiar. It allows you to view the file system on the selected device/emulator. When you start the Remote File Viewer, you will first be asked to select a Windows CE device/emulator (see Figure 16).

    Figure 16
    Figure 16. Selecting an emulator

    The Remote File Viewer then displays the file system on the selected device/emulator. You can transfer files in and out of the device as well as delete files on the device (see Figure 17).

    Figure 17
    Figure 17. The Remote File Viewer



    Remote Heap Walker

    The Remote Heap Walker displays information about the following:

    • Heap identifiers and flags for each process running on a target device (see Figure 18).
    • System memory that a process uses. The tool can help you to determine whether an application is releasing the memory it allocates (see Figure 19).

    Figure 18
    Figure 18. Processes running on a device

    Figure 19
    Figure 19. System memory used by a process

    Remote Process Viewer

    The Remote Process Viewer window displays information associated with each process running on a target device. You can use the Remote Process Viewer to kill processes that are running on a device/emulator (see Figure 20).

    Figure 20
    Figure 20. The Remote Process Viewer

    Remote Registry Editor

    The Remote Registry Editor displays the registry for a target device and enables you to add, delete, and modify registry keys and registry entries. You can also edit the registry entries on your local computer using the Remote Registry Editor (see Figure 21).

    Figure 21
    Figure 21. The Remote Registry Editor

    Remote Spy

    The Remote Spy displays messages received by windows associated with applications running on a target device (see Figure 22). Remote Spy displays a list of the windows that are open on a target device. In a separate window, the tool displays information about the messages in the message queue for the selected window.

    Figure 22
    Figure 22. The Remote Spy

    Remote Zoom-in

    The Remote Zoom-in displays a screen image from a target device. This tool is useful for capturing screen shots of your device/emulator (see Figure 23).

    Figure 23
    Figure 23. The Remote Zoom-in

    Summary

    In this article, you have seen some of the techniques and tools that make your life as a mobile application developer easier. Learning how to use the emulator to your advantage will greatly increase your productivity and ensure that your application runs on various devices without problems.

    Wei-Meng Lee (weimenglee.blogspot.com) is a technologist and founder of Developer Learning Solutions, a technology company specializing in hands-on training of the latest Microsoft technologies.

    Copyright © 2006 O'Reilly Media, Inc.

    9:02 AM | Add a comment | Permalink | Blog it | Mobile - Emulador