Deploying the Device Application to the Windows Mobile Emulator

Deploy generated code to a connected Windows Mobile device or emulator.

  1. Click the Verify icon check_16 on the toolbar to verify the device application has no errors.
  2. Click the code generation icon generate_deviceclient_16 on the toolbar.
  3. In the Generate Device Application wizard, select Windows Mobile and, optionally, select:
    Option Description
    Locale Expand this section to see a list of available locales from which you can select.
    Advanced Expand this section for advanced options:
    • Check Mobile Business Object on Sybase Unwired Platform Server – verify that the mobile business objects that are used in the device application exist on the corresponding Unwired Server.
    • Mobile Business Object Group – the mobile business object group that contains the mobile business objects you want to verify.

      To generate code for the mobile application project, click Generate Code.Use the wizard to generate the metadata classes for the selected mobile business objects.

  4. Click Next.
  5. Enter the information for the device application code generation options:
    Option Description
    Favorite Configurations Select a configuration.
    Device
    • Target device – select the device.
    • Library version – choose the Microsoft .NET version of the library used to compile the generated code.
      Note: Microsoft .NET Compact Framework 2.0 requires SP 2.0.
    Code Generation
    • Visual Studio solutions folder – accept the default or click Browse to enter the location for the Visual Studio Solutions folder.
      Note: A .cab file is generated and placed in the Visual Studio solutions folder.
    • Solution name – enter the name of the Visual Studio solution.
    • Delete solution folder prior to generation – remove existing source folders before regenerating the Visual Studio solution.
    • Generate replication-based application – select if the application has replication based synchronization.
    • Generate messaging-based application – select if the application has message based synchronization.
    Advanced

    When the device application code is generated, two projects are created—the client project, which contains the user interface screens, and the mobile application project, which contains the mobile business objects that access and update the data.

    • Client project name – enter the name of the project that contains the user interface.
    • Client project namespace – enter the namespace to use for the generated UI classes.
    • Client project assembly name – the name of the generated .exe file for the project. This is the name that appears on the mobile device.
    • Mobile application project name – the name of the mobile application project that contains the mobile business objects used in the device application.
    • Mobile application project assembly name – accept the default or enter the name for the .dll of the mobile application project.
    • Client project icon – click Browse to select an icon with which to associate the generated .exe file. This is the icon that appears on the mobile device.
    • Generate source codes for Sybase Windows frameworks – generate sources for Sybase Unwired Platform Windows frameworks, including stock screens and actions.
    • Deploy to an ActiveSync connected device or emulator – deploy the generated code to a Windows Mobile device or emulator. ActiveSync enables the transferring and installation of the application on the mobile device.
      Note: ActiveSync is for Windows XP. Windows Vista, Windows 7, and Windows 2008 uses Windows Mobile Device Center.
    • Create a shortcut in Programs – create a shortcut in the Programs folder on the device.
    • Shortcut name – enter a name for the shortcut.
    • Deployment timeout (minutes) – the maximum time to wait for deployment to the device.
    • Perform silent install – use this option only when you are deploying to the emulator (not the device itself). This enables deployment to proceed with no user input.
    • Generate metadata access classes – generate additional metadata classes that describe the attributes and parameters of the generated MBO classes.
  6. Click Start Device Emulator Manager if the Device Emulator Manager is not already running.
  7. In the Device Emulator Manager, right-click the emulator to which to deploy the application, and select Connect.
  8. When the selected emulator is connected, right-click the same emulator, and select Cradle.
    The Microsoft ActiveSync Synchronization Setup wizard launches.
  9. In the Synchronization Setup wizard, click Cancel.

    ActiveSync connects to the device emulator.

  10. In the device application code generation wizard, click Finish.
    The code generation wizard verifies the code, checks for a connected device, and compiles the code in the specified location.