Merge pull request #3072 from Mikejo5000/mikejo-br13

ktoliver · web-flow · commit 70c676f25069 · 2018-10-11T08:56:32.000-07:00
Miscellaneous edits
diff --git a/docs/debugger/error-the-web-server-could-not-find-the-requested-resource.md b/docs/debugger/error-the-web-server-could-not-find-the-requested-resource.md
@@ -19,10 +19,12 @@ ms.workload:
 ---
 # Error: The Web Server Could Not Find the Requested Resource
 Due to security considerations, IIS has returned a generic error.  
-  
- One possible cause is the security configuration of the server. IIS 6.0 and earlier versions used an add-on program, known as URLScan, to filter out suspicious and malformed requests. IIS 7.0 has built-in Request Filtering for the same purpose. In both cases, overly restrictive request filtering can prevent Visual Studio from debugging the server.  
-  
- There are numerous possible causes of this error. A few of the most common causes include a problem with the IIS installation or configuration, the web site configuration, or permissions in the file system. You can try accessing the resource with a browser. Depending on how IIS is configured you might have to use a local browser on the server or inspect the IIS error log to get a detailed error message.  
+
+One possible cause is the security configuration of the server. IIS 6.0 and earlier versions used an add-on program, known as URLScan, to filter out suspicious and malformed requests. IIS 7.0 has built-in Request Filtering for the same purpose. In both cases, overly restrictive request filtering can prevent Visual Studio from debugging the server.  
+
+Another possible cause of this error is that the W3SVC service for IIS is not started. Check that this service is started (grayed out) in the Services window (*services.msc*).
+
+There are numerous additional possible causes of this error. A few of the most common causes include a problem with the IIS installation or configuration, the web site configuration, or permissions in the file system. You can try accessing the resource with a browser. Depending on how IIS is configured, you might have to use a local browser on the server or inspect the IIS error log to get a detailed error message.  
   
  For more information on troubleshooting IIS, see [IIS Management and Administration](/iis/manage/provisioning-and-managing-iis/iis-management-and-administration).  
   
diff --git a/docs/debugger/getting-started-with-the-debugger.md b/docs/debugger/getting-started-with-the-debugger.md
@@ -25,7 +25,7 @@ This article introduces the features of the Visual Studio debugger in a step-by-
 |---------|---------|
 |  ![movie camera icon for video](../install/media/video-icon.png "Watch a video")  |    [Watch a video](https://mva.microsoft.com/en-US/training-courses-embed/getting-started-with-visual-studio-2017-17798/Debugger-Feature-tour-of-Visual-studio-2017-sqwiwLD6D_1111787171) on debugging that shows similar steps. |
 
-Although the demo app is C# and C++, the features are applicable to Visual Basic, JavaScript, and other languages supported by Visual Studio (except where noted). The screenshots are in C#. To switch between the C# and C++ sample code in this article, use the language filter in the upper right of this page.
+Although the demo app is C# and C++, the features are applicable to Visual Basic, JavaScript, and other languages supported by Visual Studio (except where noted). The screenshots are in C#.
 
 In this tutorial, you will:
 
@@ -55,6 +55,9 @@ In this tutorial, you will:
 
     Visual Studio creates the project.
 
+    > [!NOTE]
+    > To switch between the C# and C++ sample code in this article, use the language filter in the upper right of this page.
+
 4. In *Program.cs* (C#) or *get-started-debugging.cpp* (C++), replace the following code
 
     ```csharp
diff --git a/docs/debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md b/docs/debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md
@@ -160,12 +160,7 @@ You can also publish and deploy the app using the file system or other tools.
 
 In this tutorial, we are using Visual Studio 2017.
 
-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.
-
 [!INCLUDE [remote-debugger-download](../debugger/includes/remote-debugger-download.md)]
-
-> [!TIP]
-> In some scenarios, it can be most efficient to run the remote debugger from a file share. For more information, see [Run the remote debugger from a file share](../debugger/remote-debugging.md#fileshare_msvsmon).
   
 ## <a name="BKMK_setup"></a> Set up the remote debugger on Windows Server
 
diff --git a/docs/debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md b/docs/debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md
@@ -141,12 +141,7 @@ You can also publish and deploy the app using the file system or other tools.
 
 In this tutorial, we are using Visual Studio 2017.
 
-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.
-
 [!INCLUDE [remote-debugger-download](../debugger/includes/remote-debugger-download.md)]
-
-> [!TIP]
-> In some scenarios, it can be most efficient to run the remote debugger from a file share. For more information, see [Run the remote debugger from a file share](../debugger/remote-debugging.md#fileshare_msvsmon).
   
 ## <a name="BKMK_setup"></a> Set up the remote debugger on Windows Server
 
diff --git a/docs/debugger/remote-debugging-azure.md b/docs/debugger/remote-debugging-azure.md
@@ -179,8 +179,6 @@ If you're not using Web Deploy, you must publish and deploy the app using the fi
 
 In this tutorial, we are using Visual Studio 2017.
 
-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.
-
 [!INCLUDE [remote-debugger-download](../debugger/includes/remote-debugger-download.md)]
   
 ### <a name="BKMK_setup"></a> Set up the remote debugger on Windows Server
diff --git a/docs/debugger/remote-debugging.md b/docs/debugger/remote-debugging.md
@@ -42,47 +42,6 @@ If you just want to download and install the remote debugger and don't need any
 
 [!INCLUDE [remote-debugger-download](../debugger/includes/remote-debugger-download.md)]
 
-## <a name="unblock_msvsmon"></a> Unblock the download of the remote tools on Windows Server
-
-The default security settings in Internet Explorer on Windows Server can make it time-consuming to download components such as the remote tools.
-
-* Enhanced Security Configuration is enabled on Internet Explorer, which prevents you from opening websites and accessing web resources unless the domain containing the resource is explicitly allowed (that is, trusted). Although you can disable this setting, we do not recommend it because it can presents a security risk.
-
-* On Windows Server 2016, a default setting in **Internet Options** > **Security** > **Internet** > **Custom Level** > **Downloads** also disables file downloads. If you choose to download the remote tools directly on Windows Server, you must enable file download.
-
-To download the tools on Windows Server, we recommend one of the following:
-
-* Download the remote tools on a different computer such as the one running Visual Studio, and then copy the *.exe* file to Windows Server.
-
-* Run the remote debugger [from a file share](#fileshare_msvsmon) on your Visual Studio machine.
-
-* Download the remote tools directly on Windows Server and accept the prompts to add trusted sites. Modern websites often include many third-party resources, so this can result in a lot of prompts. In addition, any redirected links may need to be added manually. You can choose to add some of the trusted sites before beginning the download. Go to **Internet Options > Security > Trusted Sites > Sites** and add the following sites.
-
-  * visualstudio.microsoft.com
-  * download.visualstudio.microsoft.com
-  * about:blank
-
-  For older versions of the debugger on my.visualstudio.com, add these additional sites to make sure that login is successful:
-
-  * microsoft.com
-  * go.microsoft.com
-  * download.microsoft.com
-  * my.visualstudio.com
-  * login.microsoftonline.com
-  * login.live.com
-  * secure.aadcdn.microsoftonline-p.com
-  * msft.sts.microsoft.com
-  * auth.gfx.ms
-  * app.vssps.visualstudio.com
-  * vlscppe.microsoft.com
-  * query.prod.cms.rt.microsoft.com
-
-    If you choose to add these domains while downloading the remote tools, then choose **Add** when prompted.
-
-    ![Blocked content dialog box](../debugger/media/remotedbg-blocked-content.png)
-
-    When you download the software, you get some additional requests to grant permission to load various web site scripts and resources. On my.visualstudio.com, we recommend that you add the additional domains to make sure that login is successful.
-
 ## <a name="requirements_msvsmon"></a> Requirements
 
 [!INCLUDE [remote-debugger-requirements](../debugger/includes/remote-debugger-requirements.md)]
