Skip to content

Commit 80a6c29

Browse files
authored
Fix formatting
1 parent a0b356a commit 80a6c29

File tree

1 file changed

+49
-39
lines changed

1 file changed

+49
-39
lines changed

docs/debugger/run-windows-store-apps-in-the-simulator.md

Lines changed: 49 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -15,58 +15,65 @@ ms.workload:
1515
- "uwp"
1616
---
1717
# Run UWP apps in the simulator
18+
1819
The Visual Studio simulator for UWP apps is a desktop application that simulates a UWP app. Typically, you will want to debug on the local machine, a connected device, or a remote machine. However, in some scenarios, you may want to use the Visual Studio simulator to emulate a different physical screen size and resolution. You can also simulate common touch and rotation events and simulate network connection properties.
1920

20-
The simulator provides an environment in which you can design, develop, debug, and test UWP apps. However, before you publish your app to Microsoft Store, you should test your app on an actual device.
21+
The simulator provides an environment in which you can design, develop, debug, and test UWP apps. However, before you publish your app to Microsoft Store, you should test your app on an actual device.
2122

22-
The Visual Studio simulator for UWP apps does not run in an isolated environment on your local machine. Therefore, errors that occur in the simulator, such as a non-recoverable system-wide error, can also affect the entire machine.
23+
The Visual Studio simulator for UWP apps does not run in an isolated environment on your local machine. Therefore, errors that occur in the simulator, such as a non-recoverable system-wide error, can also affect the entire machine.
2324

2425
> [!IMPORTANT]
25-
> The Visual Studio 2015 simulator does not include the geolocation button. This is because the Windows 10 simulator does not include geolocation simulation.
26+
> The Visual Studio 2015 simulator does not include the geolocation button. This is because the Windows 10 simulator does not include geolocation simulation.
2627
2728
## <a name="BKMK_Set_the_simulator_as_the_target"></a> Set the simulator as the target
28-
To run your UWP app in the simulator, select **Simulator** from the drop-down list next to the **Start Debugging** button on the debugger **Standard** toolbar. This option is only available if your app's **Target Platform Min. Version** is less than or equal to the operating system on your development machine.
2929

30-
![Running in the Simulator](../debugger/media/vsrun_f5_simulator.png "VSRUN_F5_Simulator")
30+
To run your UWP app in the simulator, select **Simulator** from the drop-down list next to the **Start Debugging** button on the debugger **Standard** toolbar. This option is only available if your app's **Target Platform Min. Version** is less than or equal to the operating system on your development machine.
31+
32+
![Running in the Simulator](../debugger/media/vsrun_f5_simulator.png "VSRUN_F5_Simulator")
3133

3234
## <a name="BKMK_Choose_an_interaction_mode"></a> Choose an interaction mode
33-
You can choose the following interaction modes
35+
36+
You can choose the following interaction modes:
3437

3538
- ![Mouse mode button](../debugger/media/simulator_mousemodebtn.png "SIMULATOR_MouseModeBtn") Mouse mode: sets the interaction mode to mouse gestures. Mouse gestures include clicks, double-clicks, and drags.
3639

3740
- ![Start touch emulation button](../debugger/media/simulator_starttouchemulationbtn.png "SIMULATOR_StartTouchEmulationBtn") Start touch emulation: sets the interaction mode to touch gestures of a single finger. Single-finger events include tapping, dragging, and swiping.
3841

39-
![Simulator one finger target](../debugger/media/simulator_onefinger.png "SIMULATOR_OneFinger") The single target icon indicates the location of events in the simulator. Use the mouse to position the pointer.
42+
![Simulator one finger target](../debugger/media/simulator_onefinger.png "SIMULATOR_OneFinger")
43+
44+
The single target icon indicates the location of events in the simulator. Use the mouse to position the pointer.
4045

41-
![One finger touch target](../debugger/media/simulator_onefingerengaged.png "SIMULATOR_OneFingerEngaged") Press the left mouse button to activate the touch mode. For example, click the button to simulate a tap, or press and hold the button as you drag or swipe.
46+
![One finger touch target](../debugger/media/simulator_onefingerengaged.png "SIMULATOR_OneFingerEngaged")
47+
48+
Press the left mouse button to activate the touch mode. For example, click the button to simulate a tap, or press and hold the button as you drag or swipe.
4249

4350
## Pinch and Zoom
44-
Sets the interaction mode to pinch and zoom gestures of two fingers.
4551

46-
- ![Simulator two finger target](../debugger/media/simulator_twofinger.png "SIMULATOR_TwoFinger")
52+
Sets the interaction mode to pinch and zoom gestures of two fingers.
4753

48-
- The double target icon indicates the location of two fingers on the device screen.
54+
![Simulator two finger target](../debugger/media/simulator_twofinger.png)
4955

50-
- Move the mouse to position the icons over the object on the device screen.
56+
The double target icon indicates the location of two fingers on the device screen.
57+
58+
- Move the mouse to position the icons over the object on the device screen.
5159

52-
- Rotate the mouse wheel backward or forward to change the simulated distance of the two fingers before you pinch or zoom.
60+
- Rotate the mouse wheel backward or forward to change the simulated distance of the two fingers before you pinch or zoom.
5361

54-
- ![Pinch, zoom, and rotate targets](../debugger/media/simulator_twofingerengaged.png "SIMULATOR_TwoFingerEngaged")
62+
![Pinch, zoom, and rotate targets](../debugger/media/simulator_twofingerengaged.png)
5563

56-
- Press the left button and rotate the wheel backward (towards you) to zoom in (pinch).
64+
- Press the left button and rotate the wheel backward (towards you) to zoom in (pinch).
5765

58-
- Press the left button and rotate the mouse wheel forward (away from you) to zoom out (zoom).
66+
- Press the left button and rotate the mouse wheel forward (away from you) to zoom out (zoom).
5967

6068
## Object rotation
61-
The **Touch emulation rotate** button sets the interaction mode to rotation gestures using two fingers.
6269

63-
- Move the mouse to position the icons over the object on the device screen.
70+
The **Touch emulation rotate** button sets the interaction mode to rotation gestures using two fingers.
6471

65-
- Rotate the mouse wheel backward or forward to change the simulated orientation of the two fingers before you rotate the object.
72+
- Move the mouse to position the icons over the object on the device screen. Rotate the mouse wheel backward or forward to change the simulated orientation of the two fingers before you rotate the object.
6673

6774
- Press the left button and rotate the wheel backward (towards you) to rotate the object counter-clockwise. As you rotate the mouse wheel, one of the two target icons rotates around the other to indicate the relative size of the rotation.
6875

69-
- Press the left button and rotate the mouse wheel forward (away from you) to rotate the object clockwise.
76+
- Press the left button and rotate the mouse wheel forward (away from you) to rotate the object clockwise.
7077

7178
## <a name="BKMK_Enable_or_disable_Always_on_top_mode"></a> Enable or disable Always on top mode
7279
You can set the simulator window to always be on top of other windows. The **Toggle Topmost Window** button enables or disables the **Always on top** mode of the simulator window.
@@ -75,37 +82,38 @@ The Visual Studio simulator for UWP apps is a desktop application that simulates
7582
You can switch the device orientation between portrait and landscape by rotating the simulator 90 degrees in any direction.
7683

7784
> [!NOTE]
78-
> The simulator does not respect [DisplayProperties.AutoRotationPreferences](http://go.microsoft.com/fwlink/?LinkId=249460) property of a project. For example, if your project sets the orientation to `Landscape`, and you then rotate the simulator to a portrait orientation, the simulator display image will also be rotated and resized. Test these settings on an actual device.
85+
> The simulator does not respect [DisplayProperties.AutoRotationPreferences](http://go.microsoft.com/fwlink/?LinkId=249460) property of a project. For example, if your project sets the orientation to `Landscape`, and you then rotate the simulator to a portrait orientation, the simulator display image will also be rotated and resized. Test these settings on an actual device.
7986
8087
> [!NOTE]
81-
> If you rotate the simulator so that one edge of the simulator is larger than the screen it is displayed on, the simulator is automatically resized to fit within the screen. The simulator is not resized to its original size if you rotate it again.
88+
> If you rotate the simulator so that one edge of the simulator is larger than the screen it is displayed on, the simulator is automatically resized to fit within the screen. The simulator is not resized to its original size if you rotate it again.
8289
8390
## <a name="BKMK_Change_the_simulated_screen_size_and_resolution"></a> Change the simulated screen size and resolution
8491
To change the simulated screen size and resolution, choose the **Change Resolution** button on the palette and choose a new size and resolution from the list.
8592

8693
The screen size and resolution are listed as *Screen width inches, pixel width X pixel height*. Note that both the screen size and the resolution are simulated. Location co-ordinates on the simulator are translated to the co-ordinates of the selected device size and resolution.
8794

8895
> [!NOTE]
89-
> You can save scaled versions of bitmap images in your app and Windows will load the correct image for the current scale. For more information, see [Design and UI intro](/windows/uwp/layout/design-and-ui-intro). However, if you change the simulator resolution so that Windows picks a different image to fit the resolution, you have to stop and restart your debug session to view the new image.
96+
> You can save scaled versions of bitmap images in your app and Windows will load the correct image for the current scale. For more information, see [Design and UI intro](/windows/uwp/layout/design-and-ui-intro). However, if you change the simulator resolution so that Windows picks a different image to fit the resolution, you have to stop and restart your debug session to view the new image.
9097
9198
## <a name="BKMK_Capture_a_screenshot_of_your_app_for_submission_to_the_Microsoft_Store"></a> Capture a screenshot of your app for submission to Microsoft Store
9299
When you submit an app to Microsoft Store, you must include screenshots of the app.
93100

94101
> [!NOTE]
95-
> The screenshot is saved at the current resolution of the simulator. To change the resolution, choose the **Change Resolution** button.
102+
> The screenshot is saved at the current resolution of the simulator. To change the resolution, choose the **Change Resolution** button.
96103
97104
- To create screenshots of your app from the simulator, choose the **Capture screenshot to clipboard** button.
98105

99106
- To set the location where screenshots are located, choose the **Screenshot settings** button and choose the location from the shortcut menu.
100107

101-
![Screenshot settings context menu](../debugger/media/simulator_screenshotsettingscntxmnu.png "SIMULATOR_ScreenShotSettingsCntxMnu")
108+
![Screenshot settings context menu](../debugger/media/simulator_screenshotsettingscntxmnu.png)
102109

103110
## <a name="BKMK_Simulate_network_connection_properties"></a> Simulate network connection properties
104-
You can help your app's users manage the cost of metered network connections by maintaining awareness of network connection cost or data plan status changes and enabling your app to use this information to avoid incurring additional costs for roaming or exceeding a specified data transfer limit. The [Windows.Networking.Connectivity](/uwp/api/windows.networking.connectivity) APIs lets you respond to [NetworkStatusChanged](/uwp/api/windows.networking.connectivity.networkinformation) and [TriggerType](/uwp/api/windows.applicationmodel.background.systemtrigger) events that sign. See [Quickstart: Managing metered network cost constraints](https://msdn.microsoft.com/library/windows/apps/Hh750310.aspx).
105111

106-
To debug or test your network cost-aware code, the simulator can mimic properties of a network that are exposed through the [ConnectionProfile](/uwp/api/windows.networking.connectivity.connectionprofile) object returned by [GetInternetConnectionProfile](/uwp/api/windows.networking.connectivity.networkinformation).
112+
You can help your app's users manage the cost of metered network connections by maintaining awareness of network connection cost or data plan status changes and enabling your app to use this information to avoid incurring additional costs for roaming or exceeding a specified data transfer limit. The [Windows.Networking.Connectivity](/uwp/api/windows.networking.connectivity) APIs lets you respond to [NetworkStatusChanged](/uwp/api/windows.networking.connectivity.networkinformation) and [TriggerType](/uwp/api/windows.applicationmodel.background.systemtrigger) events that sign. See [Quickstart: Managing metered network cost constraints](https://msdn.microsoft.com/library/windows/apps/Hh750310.aspx).
113+
114+
To debug or test your network cost-aware code, the simulator can mimic properties of a network that are exposed through the [ConnectionProfile](/uwp/api/windows.networking.connectivity.connectionprofile) object returned by [GetInternetConnectionProfile](/uwp/api/windows.networking.connectivity.networkinformation).
107115

108-
To simulate network properties:
116+
To simulate network properties:
109117

110118
1. On the simulator toolbar, choose the **Change network properties** button.
111119

@@ -123,24 +131,26 @@ The Visual Studio simulator for UWP apps is a desktop application that simulates
123131

124132
7. Choose **Set Properties** to simulate the network properties by triggering a foreground [NetworkStatusChanged](/uwp/api/windows.networking.connectivity.networkinformation) event and a background [SystemTrigger](/uwp/api/windows.applicationmodel.background.systemtrigger) of type **NetworkStateChange**.
125133

126-
**More information about managing network connections**
134+
For more information about managing network connections, see:
127135

128-
[Quickstart: Managing metered network cost constraints](https://msdn.microsoft.com/library/windows/apps/Hh750310.aspx)
136+
[Quickstart: Managing metered network cost constraints](https://msdn.microsoft.com/library/windows/apps/Hh750310.aspx)
129137

130-
[Network information sample](https://code.msdn.microsoft.com/windowsapps/Network-Information-Sample-63aaa201)
138+
[Network information sample](https://code.msdn.microsoft.com/windowsapps/Network-Information-Sample-63aaa201)
131139

132-
[Analyze energy use](../profiling/analyze-energy-use-in-store-apps.md)
140+
[Analyze energy use](../profiling/analyze-energy-use-in-store-apps.md)
133141

134-
[Windows.Networking.Connectivity](/uwp/api/windows.networking.connectivity)
142+
[Windows.Networking.Connectivity](/uwp/api/windows.networking.connectivity)
135143

136-
[How to respond to system events with background tasks](/previous-versions/windows/apps/hh977058(v=win.10))
144+
[How to respond to system events with background tasks](/previous-versions/windows/apps/hh977058(v=win.10))
137145

138-
[How to trigger suspend, resume, and background events in UWP apps](how-to-trigger-suspend-resume-and-background-events-for-windows-store-apps-in-visual-studio.md)
146+
[How to trigger suspend, resume, and background events in UWP apps](how-to-trigger-suspend-resume-and-background-events-for-windows-store-apps-in-visual-studio.md)
139147

140148
## <a name="BKMK_Navigate_the_simulator_with_the_keyboard"></a> Navigate the simulator with the keyboard
141-
You can navigate the simulator toolbar by pressing **CTRL + ALT + Up Arrow** to switch focus from the simulator window to the simulator toolbar. Use the **Up Arrow** and the **Down Arrow** to move between toolbar buttons.
142149

143-
You can shut down the simulator by pressing **CTRL + ALT + F4**.
150+
You can navigate the simulator toolbar by pressing **CTRL + ALT + Up Arrow** to switch focus from the simulator window to the simulator toolbar. Use the **Up Arrow** and the **Down Arrow** to move between toolbar buttons.
151+
152+
You can shut down the simulator by pressing **CTRL + ALT + F4**.
153+
154+
## See also
144155

145-
## See Also
146-
- [Run apps from Visual Studio](/visualstudio/debugger/debugging-windows-store-and-windows-universal-apps)
156+
- [Run apps from Visual Studio](/visualstudio/debugger/debugging-windows-store-and-windows-universal-apps)

0 commit comments

Comments
 (0)