Merge pull request #15298 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-22 22:00 UTC

Author: learn-build-service-prod[bot]

docs/debugger/debug-with-copilot.md

@@ -57,6 +57,7 @@ In addition, Copilot provides more precise help for some targeted scenarios, suc
 |Conditional breakpoints and tracepoints|See [Get suggestions with conditional breakpoints and tracepoints](#get-suggestions-with-conditional-breakpoints-and-tracepoints) in this article.|
 |Quick Actions (light bulb)|See [Get AI assistance with Quick Actions](../ide/quick-actions.md#get-ai-assistance).|
 |IEnumerable tabular visualizer|See [Get AI assistance](../debugger/view-data-in-tabular-visualizer.md#get-ai-assistance).|
+|Auto-detect and format in Text Visualizer|See [Auto-detect and format](../debugger/view-strings-visualizer.md#auto-detect-and-format). Copilot automatically identifies encoded or compressed strings and decodes them in a single click.|
 |Inline return values|See [View return values of method calls](../debugger/autos-and-locals-windows.md#view-inline-return-values-of-method-calls-in-the-code-editor).|
 |Inline values|See [View inline values](../debugger/autos-and-locals-windows.md#view-inline-values).|
 |Multithreaded debugging|See [Get AI assistance with Threads view](../debugger/using-the-parallel-stacks-window.md#get-ai-assistance).|

docs/debugger/debugging-absolute-beginners.md

@@ -12,9 +12,9 @@ ms.subservice: debug-diagnostics
 ---
 # Debug for absolute beginners
 
-Without fail, the code we write as software developers doesn’t always do what we expected it to do. Sometimes it does something completely different! When the unexpected happens, the next task is to figure out why, and although we might be tempted to just keep staring at our code for hours, it's easier and more efficient to use a debugging tool or debugger.
+Without fail, the code we write as software developers doesn't always do what we expected it to do. Sometimes it does something completely different! When the unexpected happens, the next task is to figure out why, and although we might be tempted to just keep staring at our code for hours, it's easier and more efficient to use a debugging tool or debugger.
 
-A debugger, unfortunately, isn’t something that can magically reveal all the problems or “bugs” in our code. *Debugging* means to run your code step by step in a debugging tool like Visual Studio, to find the exact point where you made a programming mistake. You then understand what corrections you need to make in your code and debugging tools often allow you to make temporary changes so you can continue running the program.
+A debugger, unfortunately, isn't something that can magically reveal all the problems or "bugs" in our code. *Debugging* means to run your code step by step in a debugging tool like Visual Studio, to find the exact point where you made a programming mistake. You then understand what corrections you need to make in your code and debugging tools often allow you to make temporary changes so you can continue running the program.
 
 Using a debugger effectively is also a skill that takes time and practice to learn but is ultimately a fundamental task for every software developer. In this article, we introduce the core principles of debugging and provide tips to get you started.
 
@@ -38,7 +38,7 @@ Before you investigate a bug or an error, think of the assumptions that made you
 
 * Are you using an API correctly? Maybe you used the right API but didn't use it in the right way.
 
-* Does your code contain any typos? Some typos, like a simple misspelling of a variable name, can be difficult to see, especially when working with languages that don’t require variables to be declared before they’re used.
+* Does your code contain any typos? Some typos, like a simple misspelling of a variable name, can be difficult to see, especially when working with languages that don't require variables to be declared before they're used.
 
 * Did you make a change to your code and assume it's unrelated to the problem that you're seeing?
 
@@ -57,7 +57,7 @@ When you normally run an app, you see errors and incorrect results only after th
 
 When you run an app within a debugger, also called *debugging mode*, the debugger actively monitors everything that's happening as the program runs. It also allows you to pause the app at any point to examine its state and then step through your code line by line to watch every detail as it happens.
 
-In Visual Studio, you enter debugging mode by using **F5** (or the **Debug** > **Start Debugging** menu command or the **Start Debugging** button :::image type="content" source="../debugger/media/dbg-tour-start-debugging.png" alt-text="Icon showing Start Debugging button."::: in the Debug Toolbar). If any exceptions occur, Visual Studio’s Exception Helper takes you to the exact point where the exception occurred and provides other helpful information. For more information on how to handle exceptions in your code, see [Debugging techniques and tools](../debugger/write-better-code-with-visual-studio.md#fix-an-exception).
+In Visual Studio, you enter debugging mode by using **F5** (or the **Debug** > **Start Debugging** menu command or the **Start Debugging** button :::image type="content" source="../debugger/media/dbg-tour-start-debugging.png" alt-text="Icon showing Start Debugging button."::: in the Debug Toolbar). If any exceptions occur, Visual Studio's Exception Helper takes you to the exact point where the exception occurred and provides other helpful information. For more information on how to handle exceptions in your code, see [Debugging techniques and tools](../debugger/write-better-code-with-visual-studio.md#fix-an-exception).
 
 If you didn't get an exception, you probably have a good idea of where to look for the problem in your code. This step is where you use *breakpoints* with the debugger to give yourself a chance to examine your code more carefully. Breakpoints are the most basic and essential feature of reliable debugging. A breakpoint indicates where Visual Studio should pause your running code so you can take a look at the values of variables, or the behavior of memory, the sequence in which code runs.
 

docs/debugger/find-your-debugging-task.yml

@@ -34,7 +34,7 @@ sections:
 
           - **How do I log information to the Output window under configurable conditions without modifying or stopping my code?**
               
-             Tracepoints allow you to log information to the Output window under configurable conditions without modifying or stopping your code. For more information, see [Use tracepoints in the Visual Studio debugger](../debugger/using-tracepoints.md)         
+             Tracepoints allow you to log information to the Output window under configurable conditions without modifying or stopping your code. For more information, see [Use tracepoints in the Visual Studio debugger](../debugger/using-tracepoints.md).         
                     
           - **Manage and keep track of my breakpoints**
           
@@ -100,17 +100,17 @@ sections:
            
              See [Attach to a running processes](attach-to-running-processes-with-the-visual-studio-debugger.md).
 
-          - **How can I to attach to the same application repeatedly?** 
+          - **How can I attach to the same application repeatedly?** 
             
              You can use **Reattach to Process** (**Shift+Alt+P**) to easily allow you to start debugging your application in one click without needing to go through the Attach to Process dialog every time.
-             See [Reattach to a process](attach-to-running-processes-with-the-visual-studio-debugger.md#BKMK_reattach)
+             See [Reattach to a process](attach-to-running-processes-with-the-visual-studio-debugger.md#BKMK_reattach).
 
       - question: |
           Debug multithreaded applications
         answer: |
           - **How can I debug a multi-threaded application? Or, is my application in a hung state?**
 
-            See [Parallel Stacks window](using-the-parallel-stacks-window.md) further troubleshooting
+            See [Parallel Stacks window](using-the-parallel-stacks-window.md) further troubleshooting.
 
           - **How can I view the order in which functions are called?**
 
@@ -145,7 +145,7 @@ sections:
   
             Just My Code is a Visual Studio debugging feature that automatically steps over calls to system, framework, and other non-user code. 
             In the Call Stack window, Just My Code collapses these calls into [External Code] frames. 
-            See [Debug only user code with Just My Code](just-my-code.md)
+            See [Debug only user code with Just My Code](just-my-code.md).
 
           - **How can I view or debug the raw assembly instructions that my program is executing?** 
 
@@ -154,17 +154,17 @@ sections:
           - **Can I see source code for .NET Libraries?**  
 
             Enable Microsoft Symbol Servers from Debug > Options > Symbols in order to download symbols and source for .NET Libraries.
-            See [Specify symbol](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md)
+            See [Specify symbol](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md).
 
           - **How can I load PDBs from a specific or shared location or server?** 
 
             Configure your Symbol Servers from Debug > Options > Symbols. 
-            See [Specify symbol](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md)
+            See [Specify symbol](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md).
 
           - **How can I never load a specific PDB? Or, how can I always load one?**
 
             Configure your Include and Exclude Lists in Debug > Options > Symbols.  
-            See [Specify symbol](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md)
+            See [Specify symbol](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md).
 
       - question: |
           Configure debugging
@@ -184,12 +184,12 @@ sections:
           - **Do I need to save a dump?**
 
              While stopped at an error or breakpoint during debugging, select **Debug > Save Dump As**.
-             See [Dump files](using-dump-files.md)
+             See [Dump files](using-dump-files.md).
 
           - **How do I analyze a dump file?**
 
             Open the dump by choosing **File > Open** in Visual Studio. To start debugging, select **Debug with Managed Only**, **Debug with Native Only**, **Debug with Mixed**, or **Debug with Managed Memory**.
-            See [Dump files](using-dump-files.md)
+            See [Dump files](using-dump-files.md).
 
           - **Can I edit code during a debugging session?**
           
@@ -201,7 +201,7 @@ sections:
           
           - **How can I fix performance issues?**
           
-            See [First look at the profiling tools](../profiling/profiling-feature-tour.md)
+            See [First look at the profiling tools](../profiling/profiling-feature-tour.md).
 
           - **How do I fix an exception?**
 

docs/debugger/media/visualstudio/text-visualizer-text-decode.gif

@@ -1,8 +1,9 @@
 ---
 title: "View strings in a string visualizer"
 description: Use the string visualizer in Visual Studio debugger to view text strings, XML, HTML, and JSON. You can view other object types, including DataSet and DataTable.
-ms.date: "01/12/2026"
+ms.date: "04/20/2026"
 ms.topic: how-to
+ms.custom: awp-ai
 f1_keywords:
   - "vs.debug.stringviewer"
 dev_langs:
@@ -19,6 +20,7 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # View strings in a string visualizer in Visual Studio
 
 While you are debugging in Visual Studio, you can view strings with the built-in string visualizer. The string visualizer shows strings that are too long for a data tip or debugger window. It can also help you identify malformed strings.
@@ -67,6 +69,14 @@ To search for a sub-string in the text visualizer, press **Ctrl + F** to open th
 ![Screenshot of search within the text visualizer.](../debugger/media/visualstudio/debug-string-visualizer-text-search.png "Text string visualizer")
 
 If you need to read content behind the search box, hold down **Ctrl** and the search box becomes transparent.
+
+### Auto-detect and format
+
+The **Auto-detect and format** button in the top-right of the Text Visualizer automatically identifies the encoding or compression format of a string and applies the necessary transformations in a single click. Powered by Copilot, this feature instantly converts complex data, such as GZip-compressed Base64, into readable text — removing the need for manual decoding steps or external tools.
+
+To use this feature, select the **Auto-detect and format** button while viewing a string in the Text Visualizer.
+
+![Gif showing Auto-detect and format in the Text Visualizer.](../debugger/media/visualstudio/text-visualizer-text-decode.gif "Auto-detect and format in the Text Visualizer")
 ::: moniker-end
 
 ### View JSON string data

docs/debugger/view-strings-visualizer.md

@@ -22,7 +22,7 @@ A debugger is a very specialized developer tool that attaches to your running ap
 
 ## Debug mode vs. running your app
 
-When you run your app in Visual Studio for the first time, you may start it by pressing the green arrow button ![Start Debugging](../debugger/media/dbg-tour-start-debugging.png "Start Debugging") in the toolbar (or **F5**). By default, the **Debug** value appears in the drop-down to the left. If you are new to Visual Studio, this can leave the impression that debugging your app has something to do with running your app--which it does--but these are fundamentally two very different tasks.
+When you run your app in Visual Studio for the first time, you may start it by pressing the green arrow button ![Start Debugging](../debugger/media/dbg-tour-start-debugging.png "Start Debugging") in the toolbar (or **F5**). By default, the **Debug** value appears in the drop-down to the left. If you are new to Visual Studio, this can leave the impression that debugging your app has something to do with running your app—which it does—but these are fundamentally two very different tasks.
 
 ![Select a Debug build](../debugger/media/what-is-debugging-debug-build.png)
 
@@ -36,7 +36,7 @@ When you switch this setting, you change your project from a debug configuration
 
 ## When to use a debugger
 
-The debugger is an essential tool to find and fix bugs in your apps. However, context is king, and it is important to leverage all the tools at your disposable to help you quickly eliminate bugs or errors. Sometimes, the right "tool" might be a better coding practice. By learning when to use the debugger vs. some other tool, you will also learn how to use the debugger more effectively.
+The debugger is an essential tool to find and fix bugs in your apps. However, context is king, and it is important to leverage all the tools at your disposal to help you quickly eliminate bugs or errors. Sometimes, the right "tool" might be a better coding practice. By learning when to use the debugger vs. some other tool, you will also learn how to use the debugger more effectively.
 
 ## Related content
 

docs/debugger/what-is-debugging.md

@@ -1,8 +1,8 @@
 ---
 title: "Tutorial: Create C# ASP.NET Core web application"
 description: Create a web application in the Visual Studio integrated development environment (IDE) by using C# and ASP.NET Core, make changes to the app, and run the app.
-author: anandmeg
-ms.author: meghaanand
+author: MikeJo5000
+ms.author: mikejo
 manager: mijacobs
 ms.subservice: general-ide
 ms.topic: tutorial

docs/get-started/csharp/tutorial-aspnet-core.md

@@ -6,8 +6,8 @@ ms.date: 02/11/2026
 ms.subservice: general-ide
 ms.topic: tutorial
 ms.devlang: csharp
-author: anandmeg
-ms.author: meghaanand
+author: MikeJo5000
+ms.author: mikejo
 manager: mijacobs
 monikerRange: ">=vs-2022"
 dev_langs:

docs/get-started/csharp/tutorial-console-part-2.md

@@ -6,8 +6,8 @@ ms.date: 12/15/2025
 ms.subservice: general-ide
 ms.topic: tutorial
 ms.devlang: csharp
-author: anandmeg
-ms.author: meghaanand
+author: MikeJo5000
+ms.author: mikejo
 manager: mijacobs
 dev_langs:
   - CSharp

docs/get-started/csharp/tutorial-console.md

@@ -5,8 +5,8 @@ ms.custom: vs-acquisition
 ms.date: 09/14/2021
 ms.subservice: general-ide
 ms.topic: tutorial
-author: anandmeg
-ms.author: meghaanand
+author: MikeJo5000
+ms.author: mikejo
 manager: mijacobs
 dev_langs:
 - CSharp