You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: hub/advanced-settings/sudo/index.md
+15-4Lines changed: 15 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,15 +49,26 @@ Update `<configuration_option>` to either `forceNewWindow`, `disableInput`, or `
49
49
50
50
To use Sudo for Windows, simply prepend `sudo` to the command you want to run as an administrator. For example, to run `netstat -ab` as an administrator, you would run `sudo netstat -ab` in your console window.
51
51
52
+
### Common developer scenarios
53
+
54
+
Here are some common scenarios where developers might use sudo:
55
+
56
+
-**Editing system files**: `sudo notepad C:\Windows\System32\drivers\etc\hosts`
> For development work involving system directories like `C:\Windows\`, consider using development environments or alternative approaches when possible. Sudo should be used judiciously and only when elevated permissions are truly necessary.
62
+
52
63
Because `sudo` elevates the targeted process to run with administrator-level permission, a prompt will open asking you to verify that you want to continue.
53
64
54
65
## Security Considerations
55
66
56
-
There are risks associated with running sudo in the **Input closed** (`inputClosed`) or **Inline** (`normal`) configurations. It is possible for malicious processes to attempt to drive the elevated process using the connection established by the unelevated sudo.exe and the elevated sudo.exe process.
67
+
There are risks associated with running sudo in the **Input closed** (`disableInput`) or **Inline** (`normal`) configurations. It is possible for malicious processes to attempt to drive the elevated process using the connection established by the unelevated sudo.exe and the elevated sudo.exe process.
57
68
58
-
The `inputClosed` configuration option mitigates risk by closing the input handle. Disconnecting the input handle from the current console window means that unelevated processes cannot send input to the elevated process.
69
+
The `disableInput` configuration option mitigates risk by closing the input handle. Disconnecting the input handle from the current console window means that unelevated processes cannot send input to the elevated process.
59
70
60
-
The `inline` configuration option runs the elevated process in the current window and the process is able to receive input from the current console session. An unelevated process can send input to the elevated process within the same console windows or get information from the output in the current windows in this configuration.
71
+
The `inline` configuration option runs the elevated process in the current window and the process is able to receive input from the current console session. An unelevated process can send input to the elevated process within the same console window or get information from the output in the current window in this configuration.
61
72
62
73
## FAQ
63
74
@@ -75,7 +86,7 @@ The `inline` configuration option runs the elevated process in the current windo
75
86
76
87
-`sudo` can only be elevated via the User Account Control (UAC) security feature designed to protect the operating system from unauthorized changes using verification prompt.
77
88
78
-
You should consider your particular use-case and plan to use the command that best meets your needs. You should also consider the security implications of running sudo in the `inputClosed` and `normal` modes. The default `forceNewWindow` configuration option is recommended unless you are familiar and comfortable with the risks associated with the other `sudo` configurations.
89
+
You should consider your particular use-case and plan to use the command that best meets your needs. You should also consider the security implications of running sudo in the `disableInput` and `normal` modes. The default `forceNewWindow` configuration option is recommended unless you are familiar and comfortable with the risks associated with the other `sudo` configurations.
Copy file name to clipboardExpand all lines: hub/apps/get-started/start-here.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,10 +10,9 @@ ms.collection: windows11
10
10
11
11
# Setup and tooling for WinUI
12
12
13
-
Welcome to Windows app development. This guide will take you through the steps needed to begin creating your first app with WinUI. It will also point you to resources that will help you learn more about Windows development.
13
+
This guide walks you through setting up your WinUI and Windows App SDK development environment in Visual Studio and creating your first app.
14
14
15
-
16
-
## 1. Enable Developer Mode
15
+
### 1. Enable Developer Mode
17
16
18
17
Windows has a special mode for developers that adjusts security settings so you can run the apps you're working on. You need to enable Developer Mode before you can build, deploy, and test your app by using Visual Studio.
19
18
@@ -28,7 +27,7 @@ To enable Developer Mode:
28
27
For more information about Developer Mode, see [Settings for developers](/windows/advanced-settings/developer-mode).
29
28
30
29
31
-
## 2. Install Visual Studio and required workloads
30
+
###2. Install Visual Studio and required workloads
32
31
33
32
Use [Visual Studio](/visualstudio/ide/), Microsoft’s powerful IDE, to build, debug, and deploy your WinUI app. It offers ready-to-use project templates for Windows and other platforms to help you get started quickly.
34
33
@@ -75,7 +74,7 @@ On the **Workloads** tab of the Visual Studio Installer app, select the followin
75
74
76
75
---
77
76
78
-
## 3. Create and launch your first WinUI app
77
+
###3. Create and launch your first WinUI app
79
78
80
79
Visual Studio project templates include all the files you need to quickly create your app. In fact, after you create your project from a WinUI app template, you already have an app that you can run, and then add your code to.
81
80
@@ -105,7 +104,7 @@ Congratulations, you've just built your first WinUI app! Continue with the next
105
104
## Next steps
106
105
107
106
> [!div class="nextstepaction"]
108
-
> [Build your first notetaking app with WinUI](../tutorials/winui-notes/intro.md)
107
+
> [Build your first app with WinUI](../tutorials/winui-notes/intro.md)
109
108
110
109
* To get an idea of what WinUI offers, check out the WinUI Gallery app.
0 commit comments