MicrosoftDocs · fenxu · Dec 14, 2018 · Dec 14, 2018 · Dec 15, 2018 · Dec 15, 2018
diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json
@@ -1,22 +1,6 @@
 {
   "build_entry_point": "docs",
   "docsets_to_publish": [
-    {
-      "docset_name": "connected-environment",
-      "build_source_folder": "connected-environment",
-      "build_output_subfolder": "connected-environment",
-      "locale": "en-us",
-      "monikers": [],
-      "moniker_ranges": [],
-      "open_to_public_contributors": false,
-      "type_mapping": {
-        "Conceptual": "Content",
-        "ManagedReference": "Content",
-        "RestApi": "Content"
-      },
-      "build_entry_point": "docs",
-      "template_folder": "_themes"
-    },
     {
       "docset_name": "docs",
       "build_source_folder": "docs",

diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -682,17 +682,22 @@
         },
         {
             "source_path": "docs/debugger/first-look-at-the-debugger.md",
-            "redirect_url": "/visualstudio/debugger/getting-started-with-the-debugger",
+            "redirect_url": "/visualstudio/debugger/debugger-feature-tour.md",
             "redirect_document_id": false
         },
         {
             "source_path": "docs/debugger/debugger-basics.md",
-            "redirect_url": "/visualstudio/debugger/getting-started-with-the-debugger",
+            "redirect_url": "/visualstudio/debugger/debugger-feature-tour.md",
             "redirect_document_id": false
         },
         {
             "source_path": "docs/debugger/getting-started-with-the-debugger-vb.md",
-            "redirect_url": "/visualstudio/get-started/visual-basic/getting-started-with-the-debugger-vb",
+            "redirect_url": "/visualstudio/get-started/visual-basic/tutorial-debugger",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/debugger/getting-started-with-the-debugger.md",
+            "redirect_url": "/visualstudio/debugger/debugger-feature-tour.md",
             "redirect_document_id": false
         },
         {
@@ -6882,6 +6887,11 @@
             "redirect_url": "/visualstudio/get-started/csharp/tutorial-aspnet-core",
             "redirect_document_id": true
         },
+        {
+            "source_path": "docs/ide/tutorial-csharp-console.md",
+            "redirect_url": "/visualstudio/get-started/csharp/tutorial-console",
+            "redirect_document_id": true
+        },        
         {
             "source_path": "docs/ide/tutorial-visual-basic-console.md",
             "redirect_url": "/visualstudio/get-started/visual-basic/tutorial-console",
@@ -7071,6 +7081,11 @@
             "source_path": "docs/reference/synchronized-settings-environment-options-dialog-box.md",
             "redirect_url": "/visualstudio/ide/reference/accounts-environment-options-dialog-box",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/extensibility/buildprojectonload-visual-studio-templates.md",
+            "redirect_url": "/visualstudio/extensibility/buildonload-visual-studio-templates",
+            "redirect_document_id": false
         }
     ]
 }
diff --git a/connected-environment/breadcrumb/toc.yml b/connected-environment/breadcrumb/toc.yml
diff --git a/connected-environment/docfx.json b/connected-environment/docfx.json
diff --git a/docs/ai/media/Tensorflow_logo.png b/docs/ai/media/Tensorflow_logo.png
diff --git a/docs/ai/media/about/App_IDE.png b/docs/ai/media/about/App_IDE.png
diff --git a/docs/ai/media/about/TensorBoard.png b/docs/ai/media/about/TensorBoard.png
diff --git a/docs/ai/media/about/runhistory-list.png b/docs/ai/media/about/runhistory-list.png
diff --git a/docs/ai/media/manage-storage/job-history.png b/docs/ai/media/manage-storage/job-history.png
diff --git a/docs/code-quality/C26455.md b/docs/code-quality/C26455.md
@@ -0,0 +1,28 @@
+---
+title: C26455
+ms.date: 12/14/2018
+ms.prod: visual-studio-dev15
+ms.technology: vs-ide-code-analysis
+ms.topic: "conceptual"
+f1_keywords:
+  - "C26455"
+helpviewer_keywords:
+  - "C26455"
+ms.assetid: 27e86063-d969-49d8-8912-dcc2dc57249f
+author: kylereedmsft
+ms.author: kylereed
+manager: annagrin
+ms.workload:
+  - "multiple"
+---
+# C26455 DEFAULT_CTOR_NOEXCEPT
+
+The C++ Core Guidelines suggest that default constructors shouldn't do anything that can throw. If the default constructor is allowed to throw, operations such as move and swap will also throw which is undesirable because move and swap should always succeed. Parameterized constructors may throw.
+
+## Remarks
+
+Consider the default constructors of the STL types, like `std::vector`. In these implementations, the default constructors initialize internal state without making allocations. In the `std::vector` case, the size is set to 0 and the internal pointer is set to `nullptr`. The same pattern should be followed for all default constructors.
+
+## See also
+
+- [C++ Core Guideline for this warning](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#Rf-noexcept)
diff --git a/docs/code-quality/C26456.md b/docs/code-quality/C26456.md
@@ -0,0 +1,22 @@
+---
+title: C26456
+ms.date: 12/14/2018
+ms.prod: visual-studio-dev15
+ms.technology: vs-ide-code-analysis
+ms.topic: "conceptual"
+f1_keywords:
+  - "C26456"
+helpviewer_keywords:
+  - "C26456"
+ms.assetid: 3a3ad636-0938-40b5-93ce-169322e2ff23
+author: kylereedmsft
+ms.author: kylereed
+manager: annagrin
+ms.workload:
+  - "multiple"
+---
+# C26456 DONT_HIDE_OPERATORS
+
+Hiding base methods that aren't virtual is error prone and makes code harder to read.
+
+[C++ Core Guideline for this warning](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#c128-virtual-functions-should-specify-exactly-one-of-virtual-override-or-final)
diff --git a/docs/code-quality/C26476.md b/docs/code-quality/C26476.md
@@ -0,0 +1,22 @@
+---
+title: C26476
+ms.date: 12/14/2018
+ms.prod: visual-studio-dev15
+ms.technology: vs-ide-code-analysis
+ms.topic: "conceptual"
+f1_keywords:
+  - "C26476"
+helpviewer_keywords:
+  - "C26476"
+ms.assetid: bb2b3b26-9a84-4d81-8bae-ad9a5577c8a6
+author: kylereedmsft
+ms.author: kylereed
+manager: annagrin
+ms.workload:
+  - "multiple"
+---
+# C26476 USE_VARIANT
+
+`std::variant` provides a type-safe alternative to `union` and should be preferred in modern code.
+
+[C++ Core Guideline for this warning](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#Ru-naked)
diff --git a/docs/code-quality/C26477.md b/docs/code-quality/C26477.md
@@ -0,0 +1,22 @@
+---
+title: C26477
+ms.date: 12/14/2018
+ms.prod: visual-studio-dev15
+ms.technology: vs-ide-code-analysis
+ms.topic: "conceptual"
+f1_keywords:
+  - "C26477"
+helpviewer_keywords:
+  - "C26477"
+ms.assetid: d5395efc-5eb2-4e82-9b45-fcd5ff4577bf
+author: kylereedmsft
+ms.author: kylereed
+manager: annagrin
+ms.workload:
+  - "multiple"
+---
+# C26477 USE_NULLPTR_NOT_CONSTANT
+
+`nullptr` has a special type `nullptr_t` that allows overloads with special null handling. Using `0` or `NULL` in place of `nullptr` bypasses the type safety and deduction that `nullptr` provides.
+
+[C++ Core Guideline for this warning](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#Res-nullptr)
diff --git a/docs/code-quality/C26486.md b/docs/code-quality/C26486.md
@@ -0,0 +1,47 @@
+---
+title: C26486
+ms.date: 12/14/2018
+ms.prod: visual-studio-dev15
+ms.technology: vs-ide-code-analysis
+ms.topic: "conceptual"
+f1_keywords:
+  - "C26486"
+helpviewer_keywords:
+  - "C26486"
+ms.assetid: d5395efc-5eb2-4e82-9b45-fcd5ff4577bf
+author: kylereedmsft
+ms.author: kylereed
+manager: annagrin
+ms.workload:
+  - "multiple"
+---
+# C26486 LIFETIMES_FUNCTION_PRECONDITION_VIOLATION
+
+Don't pass a pointer that may be invalid (dangling) as a parameter to a function.
+
+```cpp
+void use(int*);
+
+void ex1()
+{
+    int* px;
+    {
+        int x;
+        px = &x;
+    }
+
+    use(px);  // px is a dangling pointer
+}
+```
+
+## Remarks
+
+The Lifetime guidelines from the C++ core guidelines outline a contract that code can follow which will enable more thorough static memory leak and dangling pointer detection. The basic ideas behind the guidelines are:
+
+- Never dereference an invalid (dangling) or known-null pointer
+- Never return (either formal return or out parameter) any pointer from a function.
+- Never pass an invalid (dangling) pointer to any function.
+
+## See also
+
+- [C++ Core Guidelines Lifetimes Paper](https://github.com/isocpp/CppCoreGuidelines/blob/master/docs/Lifetime.pdf)
diff --git a/docs/code-quality/C26487.md b/docs/code-quality/C26487.md
@@ -0,0 +1,44 @@
+---
+title: C26487
+ms.date: 12/14/2018
+ms.prod: visual-studio-dev15
+ms.technology: vs-ide-code-analysis
+ms.topic: "conceptual"
+f1_keywords:
+  - "C26487"
+helpviewer_keywords:
+  - "C26487"
+ms.assetid: 2b0dbec3-c963-4437-8218-933717c1db98
+author: kylereedmsft
+ms.author: kylereed
+manager: annagrin
+ms.workload:
+  - "multiple"
+---
+# C26487 LIFETIMES_FUNCTION_POSTCONDITION_VIOLATION
+
+Don't allow a function to return an invalid pointer, either through the formal return or output parameters.
+
+```cpp
+int* ex1(int a)
+{
+  return &a;     // returns a dangling pointer to the stack varible 'a'
+}
+
+void ex2(int a, int** out)
+{
+  *out = &a;    // 'out' contains a dangling pointer to the stack varible 'a'
+}
+```
+
+## Remarks
+
+The Lifetime guidelines from the C++ core guidelines outline a contract that code can follow which will enable more thorough static memory leak and dangling pointer detection. The basic ideas behind the guidelines are:
+
+- Never dereference an invalid (dangling) or known-null pointer
+- Never return (either formal return or out parameter) any pointer from a function.
+- Never pass an invalid (dangling) pointer to any function.
+
+## See also
+
+- [C++ Core Guidelines Lifetimes Paper](https://github.com/isocpp/CppCoreGuidelines/blob/master/docs/Lifetime.pdf)
diff --git a/docs/code-quality/C26488.md b/docs/code-quality/C26488.md
@@ -0,0 +1,44 @@
+---
+title: C26488
+ms.date: 12/14/2018
+ms.prod: visual-studio-dev15
+ms.technology: vs-ide-code-analysis
+ms.topic: "conceptual"
+f1_keywords:
+  - "C26488"
+helpviewer_keywords:
+  - "C26488"
+ms.assetid: 2ade0d31-f259-49de-8676-cce6092fabfc
+author: kylereedmsft
+ms.author: kylereed
+manager: annagrin
+ms.workload:
+  - "multiple"
+---
+# C26488 LIFETIMES_DEREF_NULL_POINTER
+
+Don't dereference a pointer that may be null.
+
+```cpp
+void ex1()
+{
+    int* px = nullptr;
+
+    if (px)       // notice the condition is incorrect
+        return;
+
+    *px = 1;      // 'px' known to be null here
+}
+```
+
+## Remarks
+
+The Lifetime guidelines from the C++ core guidelines outline a contract that code can follow which will enable more thorough static memory leak and dangling pointer detection. The basic ideas behind the guidelines are:
+
+1) Never dereference an invalid (dangling) or known-null pointer
+2) Never return (either formal return or out parameter) any pointer from a function.
+3) Never pass an invalid (dangling) pointer to any function.
+
+## See also
+
+- [C++ Core Guidelines Lifetimes Paper](https://github.com/isocpp/CppCoreGuidelines/blob/master/docs/Lifetime.pdf)