Another option is to integrate the emulator into Visual Studio .NET so that the emulator
launches when you click Start Debug. To do this, right-click a mobile web form .aspx page, and
select Browse With from the context menu. Next, click Add; click Browse to locate the emulator
executable; click OK; provide a friendly name; and then click OK to return to the Browse With
dialog box. Then, select the newly added emulator, and click Set As Default. Note that if
the emulator takes a command-line argument, you can provide the URL as a parameter with
this syntax:
"C:\pathToEmulator\emulator.exe %URL"
To have the emulator launch by default, you will need to change a project setting. Rightclick
the project in Solution Explorer, and select Properties. Next, click the Web tab, and select
???Start external program.??? This allows you to set the path to the emulator, provide command-
line arguments, and set the working directory. Note that if the emulator does not take a commandline
parameter, you will have to manually enter the URL once the emulator is running. Once
the emulator starts browsing the web application, the mobile web application will be in debug
mode and will hit any breakpoints that are set and enabled.
This completes our overview of the mobile controls available and development model in
ASP.
Pages:
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631