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: docs/debugger/includes/remote-debugger-install-iis-role.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,6 @@ For Windows Server operating systems, use the **Add Roles and Features** wizard
20
20
21
21
22
22
23
-
On the **Role services** step, select the IIS role services you desire or accept the default role services provided.
23
+
On the **Role services** step, select the IIS role services you desire or accept the default role services provided. If you plan to deploy using Web Deploy, make sure that **IIS Management Scripts and Tools** is selected.
24
24
25
25
Proceed through the confirmation steps to install the web server role and services. A server/IIS restart is not required after installing the Web Server (IIS) role.
Copy file name to clipboardExpand all lines: docs/debugger/output-window-debugging-options-dialog-box.md
+13-11Lines changed: 13 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -21,16 +21,18 @@ ms.workload:
21
21
- "multiple"
22
22
---
23
23
# Output Window, Debugging, Options Dialog Box
24
-
You can specify which types of debugging information appear in the **Output** window. To display these options, open the **Tools** menu, click **Options**, expand the **Debugging** node, and click **Output Window**.
25
-
26
-
**General Output Settings**
24
+
You can specify which types of debugging information appear in the **Output** window. To display these options, open the **Tools** menu, click **Options**, expand the **Debugging** node, and click **Output Window**.
25
+
26
+
**General Output Settings**
27
27
This category contains controls that determine whether general debug messages appear in the **Output** window. You can specify whether each type of message appears.
28
+
29
+
**WPF Trace Settings**
30
+
This category contains controls that determine the level of WPF trace messages that appear in the **Output** window. You can specify whether each type of message appears and specify a level ranging from **Critical** to **All**.
31
+
32
+
For more information, see [How to: Display WPF Trace Information](../debugger/how-to-display-wpf-trace-information.md).
33
+
34
+
If you need to restore default settings, you can do that using **Tools** > **Import and Export Settings** > **Reset all settings**. If you only want to reset a subset of settings, save your settings in the **Import and Export Settings Wizard** before making the changes that you want to test, then import your saved settings later.
28
35
29
-
**WPF Trace Settings**
30
-
This category contains controls that determine the level of WPF trace messages that appear in the **Output** window. You can specify whether each type of message appears and specify a level ranging from **Critical** to **All**.
31
-
32
-
For more information, see [How to: Display WPF Trace Information](../debugger/how-to-display-wpf-trace-information.md).
Copy file name to clipboardExpand all lines: docs/debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md
+40-14Lines changed: 40 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ The remote debugger is supported on Windows Server starting with Windows Server
33
33
34
34
## App already running in IIS?
35
35
36
-
This article includes steps on setting up a basic configuration of IIS on Windows server and deploying the app from Visual Studio. These steps are included to make sure that requirements are in place and that you are ready to remote debug.
36
+
This article includes steps on setting up a basic configuration of IIS on Windows server and deploying the app from Visual Studio. These steps are included to make sure that the server has required components installed, that the app can run correctly, and that you are ready to remote debug.
37
37
38
38
* If your app is running in IIS and you just want to download the remote debugger and start debugging, go to [Download and Install the remote tools on Windows Server](#BKMK_msvsmon).
39
39
@@ -77,17 +77,47 @@ If you want more detailed information to install ASP.NET on IIS, see [IIS 8.0 Us
77
77
78
78
2. Restart the system (or execute **net stop was /y** followed by **net start w3svc** from a command prompt to pick up a change to the system PATH).
79
79
80
-
## (Optional) Install Web Deploy 3.6 for Hosting Servers on Windows Server
80
+
## Choose a deployment option
81
81
82
-
In some scenarios, it can be faster to import publish settings in Visual Studio instead of manually configuring deployment options. If you prefer to import publish settings instead of configuring the publishing profile in Visual Studio, see [Import publish settings and deploy to IIS](../deployment/tutorial-import-publish-settings-iis.md). Otherwise, stay in this topic and continue reading. If you complete the article on importing publish settings and deploy the app successfully, then return to this topic and start in the section on [downloading the remote tools](#BKMK_msvsmon).
82
+
If you need help to deploy the app to IIS, consider these options:
83
83
84
-
## <aname="BKMK_install_webdeploy"></a> (Optional) Install Web Deploy 3.6 on Windows Server
84
+
* Deploy by creating a publish settings file in IIS and importing the settings in Visual Studio. In some scenarios, this is a fast way to deploy your app. When you create the publish settings file, permissions are automatically set up in IIS.
* Deploy by publishing to a local folder and copying the output by a preferred method to a prepared app folder on IIS.
87
87
88
-
## <aname="BKMK_deploy_asp_net"></a> Configure ASP.NET Web site on the Windows Server computer
88
+
## (Optional) Deploy using a publish settings file
89
89
90
-
If you are importing publish settings, you can skip this section.
90
+
You can use this option create a publish settings file and import it into Visual Studio.
91
+
92
+
> [!NOTE]
93
+
> This deployment method uses Web Deploy. If you want to configure Web Deploy manually in Visual Studio instead of importing the settings, you can install Web Deploy 3.6 instead of Web Deploy 3.6 for Hosting Servers. However, if you configure Web Deploy manually, you will need to make sure that an app folder on the server is configured with the correct values and permissions (see [Configure ASP.NET Web site](#BKMK_deploy_asp_net)).
94
+
95
+
### Install and configure Web Deploy for Hosting Servers on Windows Server
After the app deploys successfully, it should start automatically. If the app does not start from Visual Studio, start the app in IIS.
108
+
109
+
1. In the **Settings** dialog box, enable debugging by clicking **Next**, choose a **Debug** configuration, and then choose **Remove additional files at destination** under the **File Publish** options.
110
+
111
+
> [!NOTE]
112
+
> If you choose a Release configuration, you disable debugging in the *web.config* file when you publish.
113
+
114
+
1. Click **Save** and then republish the app.
115
+
116
+
## (Optional) Deploy by publishing to a local folder
117
+
118
+
You can use this option to deploy your app if you want to copy the app to IIS using Powershell, RoboCopy, or you want to manually copy the files.
119
+
120
+
### <aname="BKMK_deploy_asp_net"></a> Configure the ASP.NET Web site on the Windows Server computer
91
121
92
122
1. Open Windows Explorer and create a new folder, **C:\Publish**, where you will later deploy the ASP.NET project.
93
123
@@ -105,13 +135,7 @@ If you are importing publish settings, you can skip this section.
105
135
106
136
8. With the site selected in the IIS Manager, choose **Edit Permissions**, and make sure that IUSR, IIS_IUSRS, or the user configured for the Application Pool is an authorized user with Read & Execute rights. If none of these users are present, add IUSR as a user with Read & Execute rights.
107
137
108
-
## <aname="bkmk_webdeploy"></a> (Optional) Publish and deploy the app using Web Deploy from Visual Studio
Also, you may need to read the section on [Troubleshooting ports](#bkmk_openports).
113
-
114
-
## (Optional) Publish and Deploy the app by publishing to a local folder from Visual Studio
138
+
### Publish and Deploy the app by publishing to a local folder from Visual Studio
115
139
116
140
You can also publish and deploy the app using the file system or other tools.
117
141
@@ -136,6 +160,8 @@ You can also publish and deploy the app using the file system or other tools.
136
160
137
161
In this tutorial, we are using Visual Studio 2017.
138
162
163
+
If you have trouble opening the page with the remote debugger download, see [Unblock the file download](../debugger/remote-debugging.md#unblock_msvsmon) for help.
Copy file name to clipboardExpand all lines: docs/debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md
+42-12Lines changed: 42 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Debugging between two computers connected through a proxy is not supported. Debu
29
29
30
30
## App already running in IIS?
31
31
32
-
This article includes steps on setting up a basic configuration of IIS on Windows server and deploying the app from Visual Studio. These steps are included to make sure that requirements are in place and that you are ready to remote debug.
32
+
This article includes steps on setting up a basic configuration of IIS on Windows server and deploying the app from Visual Studio. These steps are included to make sure that the server has required components installed, that the app can run correctly, and that you are ready to remote debug.
33
33
34
34
* If your app is running in IIS and you just want to download the remote debugger and start debugging, go to [Download and Install the remote tools on Windows Server](#BKMK_msvsmon).
35
35
@@ -71,17 +71,47 @@ When you download the software, you may get requests to grant permission to load
71
71
72
72
3. Restart the system (or execute **net stop was /y** followed by **net start w3svc** from a command prompt to pick up a change to the system PATH).
73
73
74
-
## (Optional) Install Web Deploy 3.6 for Hosting Servers on Windows Server
74
+
## Choose a deployment option
75
75
76
-
In some scenarios, it can be faster to import publish settings in Visual Studio instead of manually configuring deployment options. If you prefer to import publish settings instead of configuring the publishing profile in Visual Studio, see [Import publish settings and deploy to IIS](../deployment/tutorial-import-publish-settings-iis.md). Otherwise, stay in this topic and continue reading. If you complete the article on importing publish settings and deploy the app successfully, then return to this topic and start in the section on [downloading the remote tools](#BKMK_msvsmon).
76
+
If you need help to deploy the app to IIS, consider these options:
77
77
78
-
## <aname="BKMK_install_webdeploy"></a> (Optional) Install Web Deploy 3.6 on Windows Server
78
+
* Deploy by creating a publish settings file in IIS and importing the settings in Visual Studio. In some scenarios, this is a fast way to deploy your app. When you create the publish settings file, permissions are automatically set up in IIS.
* Deploy by publishing to a local folder and copying the output by a preferred method to a prepared app folder on IIS.
81
81
82
-
## <aname="BKMK_deploy_asp_net"></a> Configure ASP.NET Web site on the Windows Server computer
82
+
## (Optional) Deploy using a publish settings file
83
83
84
-
If you are importing publish settings, you can skip this section.
84
+
You can use this option create a publish settings file and import it into Visual Studio.
85
+
86
+
> [!NOTE]
87
+
> This deployment method uses Web Deploy. If you want to configure Web Deploy manually in Visual Studio instead of importing the settings, you can install Web Deploy 3.6 instead of Web Deploy 3.6 for Hosting Servers. However, if you configure Web Deploy manually, you will need to make sure that an app folder on the server is configured with the correct values and permissions (see [Configure ASP.NET Web site](#BKMK_deploy_asp_net)).
88
+
89
+
### Install and configure Web Deploy for Hosting Servers on Windows Server
After the app deploys successfully, it should start automatically. If the app does not start from Visual Studio, start the app in IIS. For ASP.NET Core, you need to make sure that the Application pool field for the **DefaultAppPool** is set to **No Managed Code**.
102
+
103
+
1. In the **Settings** dialog box, enable debugging by clicking **Next**, choose a **Debug** configuration, and then choose **Remove additional files at destination** under the **File Publish** options.
104
+
105
+
> [!NOTE]
106
+
> If you choose a Release configuration, you disable debugging in the *web.config* file when you publish.
107
+
108
+
1. Click **Save** and then republish the app.
109
+
110
+
## (Optional) Deploy by publishing to a local folder
111
+
112
+
You can use this option to deploy your app if you want to copy the app to IIS using Powershell, RoboCopy, or you want to manually copy the files.
113
+
114
+
### <aname="BKMK_deploy_asp_net"></a> Configure the ASP.NET Web site on the Windows Server computer
85
115
86
116
1. Open Windows Explorer and create a new folder, **C:\Publish**, where you will later deploy the ASP.NET project.
87
117
@@ -101,18 +131,18 @@ If you are importing publish settings, you can skip this section.
101
131
102
132
If you don't see one of these users with access, go through steps to add IUSR as a user with Read & Execute rights.
103
133
104
-
## <aname="bkmk_webdeploy"></a> (Optional) Publish and deploy the app using Web Deploy from Visual Studio
## <aname="BKMK_msvsmon"></a> Download and Install the remote tools on Windows Server
115
141
142
+
In this tutorial, we are using Visual Studio 2017.
143
+
144
+
If you have trouble opening the page with the remote debugger download, see [Unblock the file download](../debugger/remote-debugging.md#unblock_msvsmon) for help.
0 commit comments