Skip to content

Commit

Permalink
Merge pull request #344 from Microsoft/master
Browse files Browse the repository at this point in the history
merge to live
  • Loading branch information
ghogen authored Mar 22, 2017
2 parents a5d6019 + 542901b commit e86fee5
Show file tree
Hide file tree
Showing 687 changed files with 16,502 additions and 15,575 deletions.
4 changes: 2 additions & 2 deletions docs/TOC.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
# [Welcome to Visual Studio 2017!](welcome-to-visual-studio.md)
# [What's New](ide/whats-new-in-visual-studio.md)
# [Installation](install/TOC.md)
# [Visual Studio IDE Feature Tour](ide/visual-studio-ide.md)
# [Visual Studio IDE](ide/index.md)
# [Visual Basic](/dotnet/articles/visual-basic)
# [Visual C#](/dotnet/articles/csharp)
# [Visual C++](/cpp/top/visual-cpp-in-visual-studio)
# [JavaScript](javascript/javascript-in-visual-studio.md)
# [JavaScript](/scripting/javascript)
# [Python](python/getting-started-with-python.md)
# [Visual F#](/dotnet/articles/fsharp/)
# [Data Access](data-tools/TOC.md)
Expand Down
4 changes: 2 additions & 2 deletions docs/_breadcrumb/toc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -53,14 +53,14 @@
topicHref: /visualstudio/modeling/analyze-and-model-your-architecture
- name: Debugging
tocHref: /visualstudio/debugger/
topicHref: /visualstudio/debugger/debugging-in-visual-studio
topicHref: /visualstudio/debugger/index
items:
- name: DIA SDK
tocHref: /visualstudio/debugger/debug-interface-access/
topicHref: /visualstudio/debugger/debug-interface-access/debug-interface-access-sdk
- name: Profiling
tocHref: /visualstudio/profiling/
topicHref: /visualstudio/profiling/profiling-tools
topicHref: /visualstudio/profiling/index
- name: Testing
tocHref: /visualstudio/test/
topicHref: /visualstudio/test/improve-code-quality
Expand Down
4 changes: 2 additions & 2 deletions docs/csharp-ide/refactoring/sync-type-and-file.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ translation.priority.ht:
# Sync a type to a filename, or a filename to a type in C# #

<!-- VERSIONLESS -->
**This feature is available in Visual Studio 2017 and later.**
**This feature is available in Visual Studio 2017 and later. Additionally, .NET Standard projects are not yet supported for this refactoring.**

**What:** Lets you rename a type to match the filename, or rename a filename to match the type it contains.

Expand All @@ -60,4 +60,4 @@ translation.priority.ht:
![Inline result](media/synctype_result.png)

## See Also
[Refactoring (C#)](../refactoring-csharp.md)
[Refactoring (C#)](../refactoring-csharp.md)
3 changes: 1 addition & 2 deletions docs/debugger/TOC.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,4 @@
# [Debugging in Visual Studio](debugging-in-visual-studio.md)
# [Debugger Feature Tour](debugger-feature-tour.md)
# [Debugging Feature Tour](debugger-feature-tour.md)
# [What’s New for the Debugger in Visual Studio](what-s-new-for-the-debugger-in-visual-studio.md)
# [Debugger Basics](debugger-basics.md)
## [Get Started with the Debugger](getting-started-with-the-debugger.md)
Expand Down
251 changes: 100 additions & 151 deletions docs/debugger/debugger-feature-tour.md

Large diffs are not rendered by default.

102 changes: 102 additions & 0 deletions docs/debugger/first-look-at-the-debugger.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,102 @@
---
title: "Get Started with the Debugger in Visual Studio | Microsoft Docs"
ms.custom: "H1Hack27Feb2017"
ms.date: "02/07/2017"
ms.reviewer: ""
ms.suite: ""
ms.technology:
- "vs-ide-debug"
ms.tgt_pltfrm: ""
ms.topic: "get-started-article"
ms.assetid: 0b3138c4-b840-446a-a15c-10ed8e2dd050
caps.latest.revision: 5
author: "mikejo5000"
ms.author: "mikejo"
manager: "ghogen"
translation.priority.ht:
- "cs-cz"
- "de-de"
- "es-es"
- "fr-fr"
- "it-it"
- "ja-jp"
- "ko-kr"
- "pl-pl"
- "pt-br"
- "ru-ru"
- "tr-tr"
- "zh-cn"
- "zh-tw"
---
# Get Started with the Visual Studio Debugger
The Visual Studio debugger is easy to use in any language. Here we’ll show how to debug a simple C# program, but you can apply the same steps to code in other languages such as C++ and JavaScript.

To watch a video showing similar features, see [Getting Started with the Debugger](https://www.youtube.com/watch?v=FtGCi5j30YU&list=PLReL099Y5nRfw6VNvzMkv0sabT2crbSpK&index=6).

## <a name="BKMK_Start_debugging_a_VS_project"></a> Debug a Basic C# Project
Let’s start with a simple C# console application (**File / New / Project**, then select **Visual C#** and then **Console Application**). If you’ve never worked with Visual Studio before, see [Walkthrough: Create a Simple Application](../ide/walkthrough-create-a-simple-application-with-visual-csharp-or-visual-basic.md). The **Main** method just adds 1 to an integer variable 10 times and prints the result to the console:

```CSharp
static void Main(string[] args)
{
int testInt = 0;
for (int i = 1; i <= 10; i++)
{
testInt += 1;
}
Console.WriteLine(testInt);
}
```

Build this code in the **Debug** configuration. This configuration is set by default. For more information about configurations, see [Understanding Build Configurations](../ide/understanding-build-configurations.md).

Run this code in the debugger by clicking **Debug / Start Debugging** (or **Start** on the toolbar, or **F5**). The application should exit almost immediately, so you can’t actually tell whether anything was printed in the Console window.

You can stop the execution long enough to see the Console window by setting a breakpoint and then stepping ahead. To set a breakpoint, put your cursor in the `Console.WriteLine` line and click **Debug / New Breakpoint / Function Breakpoint**, or just click in the left margin at the same line. The breakpoint should look like this:

![Set a breakpoint](../debugger/media/getstartedbreakpoint.png "GetStartedBreakpoint")

For more information about breakpoints, see [Using Breakpoints](../debugger/using-breakpoints.md).

## <a name="BKMK_Inspect_Variables"></a> Inspect Variables
Debugging often involves finding variables that don't contain the values you expect at a particular point. We will show some of the ways that you can inspect variables.

Start debugging again. Execution stops before the `Console.WriteLine` code executes. You can cause it to execute by stepping ahead (click **Debug / Step Over** or **F10**). In this case you could have chosen **Step Into** (**F11**) and gotten the same result; we’ll explain the difference later on. The line with the last curly brace of the method should have turned yellow. Look at the Console window. You should see **10**.

You can hover over the **testInt** variable to view the current value in a data tip.

![DBG&#95;Basics&#95;Data&#95;Tips](../debugger/media/dbg_basics_data_tips.png "DBG_Basics_Data_Tips")

Just below the code window you should see the **Autos**, **Locals**, and **Watch** windows. These windows show the current values of variables at the time of execution. Both the **Autos** and the **Locals** windows show **testInt** with a value of **10**.

![Autos window when debugging](../debugger/media/getstartedwindows.png "GetStartedWindows")

For more information about these windows, see [Autos and Locals Windows](../debugger/autos-and-locals-windows.md).

Let’s see how the variable value changes as we walk through the program. Set a breakpoint on the `testInt += 1;` line, and restart debugging. You should see that **testInt** in the **Locals** and **Autos** windows is **0**, and **i** is **1**. When you continue debugging (**Debug / Continue**, or **Continue** on the toolbar, or **F5**), you can see that the value of **testInt** changes to **1**, then **2**, and so on. When you get tired of looking at these changes, remove the breakpoint (**Debug / Toggle Breakpoint**, or click on it in the margin), and continue debugging. If you want to remove all the breakpoints, click **Debug / Delete All Breakpoints**, or **CTRL+SHIFT+F9**, and click **Yes** on the dialog box that asks **Do you want to remove all breakpoints?**.

## Stepping Into and Over Function Calls
You can execute code in the debugger statement-by-statement (**Step Into**) or you can execute code while the debugger skips functions (**Step Over**) to quickly get to code that you're more interested in (function code is still executed). You can switch between both methods in the same debugging session.

To see the difference between **Step Into** and **Step Over**, we need to add a method that is called by another method. Add a method to the C# application and call it from the Main method. The code should look something like this:

```CSharp
static void Main(string[] args)
{
Method1();
Console.WriteLine("end");
}

private static void Method1()
{
Console.WriteLine("in Method1");
}
```

Set a breakpoint on the `Method1();` call in the Main method and start debugging. When execution breaks, click **Debug / Step Into** (or **Step Into** on the toolbar, or **F11**). Execution breaks again at the first curly brace in Method1():

![Stepping into code](../debugger/media/getstartedstepinto.png "GetStartedStepInto")

Stop debugging and start again, and when execution breaks at the breakpoint, click **Debug / Step Over** (or **Step Over** on the toolbar, or **F10**). Execution breaks again at `Console.WriteLine("end");`.

If you want to know more about navigating code with the debugger, see [Navigating through Code with the Debugger](../debugger/navigating-through-code-with-the-debugger.md).
Loading

0 comments on commit e86fee5

Please sign in to comment.