 |
|
    |
 |
|
 |
If you are developing mobile Web applications using ASP.NET
(using the ASP.NET mobile controls), you can test your content with Openwave
mobile browser simulators without leaving
Microsoft Visual Studio .NET. Basic integration of Openwave simulators with Microsoft Visual Studio .NET can be accomplished using Visual Studio configuration options, as described on the Openwave Developer Web site . More sophisticated integration can be achieved using the Openwave Simulator VS Integration add-in, which is described in this document. This add-in allows enhanced control over the Openwave 4.1.1, 6.1, and 6.2 simulators as you use them to view and debug content generated by Visual Studio. (These Openwave SDKs are available for free from the Openwave Developer Web site.) Openwave SDK 4.1.1 contains a simulator for Openwave mobile browser 4.1, which adheres to the WAP 1.1 standard and renders content in WML. SDK 6.1 and 6.2 contain Openwave mobile browser 6.1 and 6.2 respectively, which adhere to the WAP 2.0 standard and render content in XHTML Mobile Profile and CSS. You can use any combination of simulators, depending on your needs and the target devices for your market. For details on browser capabilities and device deployments, see the Openwave Developer Web site. Requirements
Installing the Openwave Simulator VS Integration add-in
Configuring the Openwave Simulator VS Integration add-in You should configure the Openwave Simulator VS Integration add-in prior to its first use.
Viewing content with the Openwave Simulator VS add-in From the Tools menu, select Openwave Simulator > View in 4.1.1, Openwave Simulator > View in 6.1, or Openwave Simulator > View in 6.2, to view the current content in the corresponding Openwave Simulator. These commands are only available when the active file is a markup file viewed in design mode; they will not be available in code view, or when working with a file that is not a markup file, such as a CSS file. When the Openwave simulators first launch, they may appear in the background, so you may have to bring them to the foreground. As you debug and make changes, you can again select one of the Openwave Simulator > View commands to update the running simulator with the revised content. You can also navigate using the Openwave simulator itself, selecting links, entering URLs in the simulator's "Go" field, or selecting the simulator's Reload command. Using the "View in All" command to view content in multiple Openwave simulators The Openwave Simulator VS add-in provides a View in All command to allow you to view content simultaneously in multiple Openwave simulators. This command will launch or update as many of the supported Openwave simulators as you have installed on your system. On initial use, this command may cause the Openwave simulators to appear in overlapped positions, but after repositioning them, they will retain their positions when the View in All command is used to update their display. Debugging with the Openwave Simulator VS add-in To debug your web application using the Openwave simulator and the Visual Studio .NET debugger, you must first specify which Openwave simulator to use in the Openwave Simulator Options dialog, as described above. Then, simply choose the Debug > Start command. The Openwave simulator will be launched and will display the running application, while the Visual Studio .NET debugger will allow you to watch variables, step through code, and perform other debugging tasks. If the Openwave simulator is already running when the Debug > Start command is chosen, the simulator will be closed and restarted, in order to allow the Visual Studio .NET debugger to attach to the simulator process. Notes
If you are using SDK 4.1.1, the first time you launch the simulator using one
of the Tools > Openwave Simulator > View commands, the
appropriate content may not be loaded correctly. The easiest workaround is to
just call the same Tools > Openwave Simulator > View command
again.
TNVSA-002
|
