Merge pull request #5746 from Mikejo5000/mikejo-nodejs

Deleted topics and refactored

Author: TedA-M

.openpublishing.redirection.json

@@ -1050,6 +1050,21 @@
       "redirect_url": "/visualstudio/xaml-tools/inspect-xaml-properties-while-debugging",
       "redirect_document_id": true
     },
+    {
+      "source_path": "docs/debugger/client-side-script-debugging.md",
+      "redirect_url": "/visualstudio/debugger/debugging-web-applications",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/debugger/how-to-attach-to-script.md",
+      "redirect_url": "/visualstudio/debugger/attach-to-running-processes-with-the-visual-studio-debugger",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/debugger/limitations-on-script-debugging.md",
+      "redirect_url": "/visualstudio/debugger/debugging-web-applications",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/designers/keyboard-shortcuts-for-xaml-designer.md",
       "redirect_url": "/visualstudio/xaml-tools/keyboard-shortcuts-for-xaml-designer",

docs/debugger/client-side-script-debugging.md

@@ -1,12 +1,7 @@
 ---
 title: "Debugging Web Applications | Microsoft Docs"
-ms.date: "11/04/2016"
+ms.date: "11/05/2019"
 ms.topic: "conceptual"
-dev_langs:
-  - "CSharp"
-  - "VB"
-  - "FSharp"
-  - "C++"
 helpviewer_keywords:
   - "debugging ASP.NET Web applications, about debugging ASP.NET Web applications"
   - "ASP.NET debugging, Web services"
@@ -20,18 +15,31 @@ ms.workload:
   - "multiple"
 ---
 # Debugging Web Applications
-This section explains how to debug several types of Web applications.
 
-## In This Section
- [Client-Side Script Debugging](../debugger/client-side-script-debugging.md)
- Discusses testing scripts and client-side scripts in [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] pages.
+This article provides links to help you debug different types of web applications.
 
-## Related Sections
- [Debug ASP.NET applications](../debugger/how-to-enable-debugging-for-aspnet-applications.md)
- Describes the steps that are required to enable debugging of [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] applications.
+- Debug ASP.NET applications
+
+  For steps that are required to enable debugging of [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] applications, see [Debug ASP.NET applications](how-to-enable-debugging-for-aspnet-applications.md).
+
+- Debug client-side script in ASP.NET
+
+  For required steps, see the blog post [Debug JavaScript in Microsoft Edge](https://devblogs.microsoft.com/visualstudio/debug-javascript-in-microsoft-edge-from-visual-studio/) and this [post for Google Chrome](https://devblogs.microsoft.com/aspnet/client-side-debugging-of-asp-net-projects-in-google-chrome).
+
+- Debug JavaScript and TypeScript
+
+  See [Debug JavaScript and TypeScript](../javascript/debug-nodejs.md).
+
+- View script documents
+
+  You can see lists of server-side and client-side script documents in the **Solution Explorer** to view. You can open any script document from **Solution Explorer**. For more information, see [How to: View Script Documents](../debugger/how-to-view-script-documents.md).
+
+- Debugging AJAX Script Applications
+
+  AJAX-enabled Web applications make heavy use of script code and pose special debugging challenges. For information about AJAX debugging techniques, see [Debugging and Tracing Ajax Applications Overview](https://msdn.microsoft.com/Library/92684ea0-7bb4-4a34-9203-3aa6394ce375).
 
 ## See also
-- [Debugging Web Applications and Script](how-to-enable-debugging-for-aspnet-applications.md)
+
 - [Debugger Settings and Preparation](../debugger/debugger-settings-and-preparation.md)
 - [First look at the debugger](../debugger/debugger-feature-tour.md)
 - [Debugging in Visual Studio](../debugger/index.yml)

docs/debugger/debugging-web-applications.md

@@ -1,6 +1,6 @@
 ---
 title: "How to: View Script Documents | Microsoft Docs"
-ms.date: "01/08/2019"
+ms.date: "11/05/2019"
 ms.topic: "conceptual"
 dev_langs:
   - "CSharp"
@@ -20,6 +20,8 @@ ms.workload:
 
 Server-side script files are visible in Solution Explorer. Client-side script files are visible only when you are in debug mode or break mode. Client-side script files appear in the **Script Documents** node.
 
+For some application types that dynamically generate pages, it is easier to enter break mode and debug when you set a breakpoint from a script document that is loaded in the browser. Similarly, you can add the `debugger` statement from a loaded script document to enter break mode. This article shows how to view these documents.
+
 > [!NOTE]
 > Previous to [!INCLUDE[vs_dev11_long](../data-tools/includes/vs_dev11_long_md.md)], client-side script files generated from server-side script appeared in the Script Explorer window.
 

docs/debugger/how-to-attach-to-script.md

@@ -654,18 +654,8 @@
         href: javascript-console-commands.md
       - name: Keyboard shortcuts (HTML and JavaScript)
         href: keyboard-shortcuts-html-and-javascript.md
-      - name: Client-side scripts
-        items:
-        - name: Client-side script debugging
-          href: client-side-script-debugging.md
-        - name: Limitations on script debugging
-          href: limitations-on-script-debugging.md
-        - name: Attach (script)
-          items:
-          - name: Attach to script
-            href: how-to-attach-to-script.md
-          - name: "Warning: Script debugging disabled"
-            href: warning-script-debugging-disabled.md
+      - name: "Warning: Script debugging disabled"
+        href: warning-script-debugging-disabled.md
     - name: WCF services
       items:
       - name: Debug WCF services

docs/debugger/how-to-view-script-documents.md

@@ -152,9 +152,9 @@ To attach the debugger from Visual Studio and hit breakpoints in client-side cod
 
     While paused in the debugger, you can examine your app state by hovering over variables and using debugger windows. You can advance the debugger by stepping through code (**F5**, **F10**, and **F11**). For more information on basic debugging features, see [First look at the debugger](../debugger/debugger-feature-tour.md).
 
-    You may hit the breakpoint in either the transpiled *.js* file or the source file, depending on which steps you followed previously, along with your environment and browser state. Either way, you can step through code and examine variables.
+    You may hit the breakpoint in either a transpiled *.js* file or source file, depending on your app type, which steps you followed previously, and other factors such as your browser state. Either way, you can step through code and examine variables.
 
-   * If you need to break into code in a TypeScript, JSX, or *.vue* source file and are unable to do it, make sure you that your environment is set up correctly, as described in the [Troubleshooting](#troubleshooting_source_maps) section.
+   * If you need to break into code in a TypeScript, JSX, or *.vue* source file and are unable to do it, make sure that your environment is set up correctly, as described in the [Troubleshooting](#troubleshooting_source_maps) section.
 
    * If you need to break into code in a transpiled JavaScript file (for example, *app-bundle.js*) and are unable to do it, remove the source map file, *filename.js.map*.
 
@@ -166,7 +166,7 @@ If you need to break into code in a TypeScript, JSX, or *.vue* source file and a
 
 * Make sure you [start the browser in debug mode](#prepare_the_browser_for_debugging).
 
-* Make sure that your source map file includes the correct reference to your source file and that it doesn't include unsupported prefixes such as *webpack:///*, which prevents the Visual Studio debugger from locating a source file. For example, a reference like *webpack:///.app.tsx* might be corrected to *./app.tsx*. You can do this manually in the source map file or through a custom build configuration. For more information, see [Generate source maps for debugging](#generate_source_maps).
+* Make sure that your source map file includes the correct relative path to your source file and that it doesn't include unsupported prefixes such as *webpack:///*, which prevents the Visual Studio debugger from locating a source file. For example, a reference like *webpack:///.app.tsx* might be corrected to *./app.tsx*. You can do this manually in the source map file (which is helpful for testing) or through a custom build configuration. For more information, see [Generate source maps for debugging](#generate_source_maps).
 
 Alternatively, if you need to break into code in a source file (for example, *app.tsx*) and are unable to do it, try using the `debugger;` statement in the source file, or set breakpoints in the Chrome Developer Tools (or F12 Tools for Microsoft Edge) instead.