You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Set debug and release configurations in Visual Studio
38
-
Visual Studio projects have separate release and debug configurations for your program. As the names imply, you build the debug version for debugging and the release version for the final release distribution.
39
-
40
-
The debug configuration of your program is compiled with full symbolic debug information and no optimization. Optimization complicates debugging, because the relationship between source code and generated instructions is more complex.
41
-
42
-
The release configuration of your program contains no symbolic debug information and is fully optimized. Debug information can be generated in .pdb files, [depending on the compiler options](#BKMK_symbols_release) that are used. Creating .pdb files can be very useful if you later have to debug your release version.
43
-
44
-
For more information about build configurations, see [Understanding Build Configurations](../ide/understanding-build-configurations.md).
45
-
46
-
You can change the build configuration from the **Build** menu, from the toolbar, or in the project's property pages. Project property pages are language-specific. The procedure below shows how to change the build configuration from the menu and the toolbar. For more information about how to change the build configuration in projects in different languages, see the See Also section below.
47
-
48
-
## Change the build configuration
49
-
50
-
1. From the **Build** menu, select **Configuration Manager**, then select **Debug** or **Release**.
51
-
52
-
2. On the toolbar, choose either **Debug** or **Release** from the **Solution Configurations** list box.
This toolbar is not available in Express editions. You can use the **Build Solution F6** and **Start Debugging F5** menu items to choose the configuration.
38
+
39
+
Visual Studio projects have separate release and debug configurations for your program. You build the debug version for debugging and the release version for the final release distribution.
40
+
41
+
In debug configuration, your program compiles with full symbolic debug information and no optimization. Optimization complicates debugging, because the relationship between source code and generated instructions is more complex.
42
+
43
+
The release configuration of your program has no symbolic debug information and is fully optimized. Debug information can be generated in .pdb files, [depending on the compiler options](#BKMK_symbols_release) that are used. Creating .pdb files can be useful if you later have to debug your release version.
44
+
45
+
For more information about build configurations, see [Understand build configurations](../ide/understanding-build-configurations.md).
46
+
47
+
You can change the build configuration from the **Build** menu, from the toolbar, or in the project's property pages. Project property pages are language-specific. The procedure below shows how to change the build configuration from the menu and the toolbar. For more information about how to change the build configuration in projects in different languages, see the [See also](#see-also) section below.
48
+
49
+
## Change the build configuration
50
+
51
+
To change the build configuration, either:
52
+
53
+
* From the **Build** menu, select **Configuration Manager**, then select **Debug** or **Release**.
54
+
55
+
or
56
+
57
+
* On the toolbar, choose either **Debug** or **Release** from the **Solution Configurations** list.
## <aname="BKMK_symbols_release"></a>Generate symbol (.pdb) files for a build
59
62
60
-
For most project types, the .pdb files are generated by default for both debug and release builds, but the default settings are different depending on your specific project type and the version of Visual Studio. You can configure whether the compiler generates .pdb files and what kind of debug information to include.
63
+
You can choose to generate symbol (.pdb) files and what debug information to include. For most project types, the compiler generates symbol files by default for debug and release builds, while other default settings differ by project type and Visual Studio version.
61
64
62
-
> [!IMPORTANT]
63
-
> The debugger will load only a .pdb file for an executable file that exactly matches the .pdb file that was created when the executable was built (that is, the .pdb must be the original or a copy of the original .pdb file). For more information see [Why does Visual Studio require debugger symbol files to exactly match the binary files that they were built with?](https://blogs.msdn.microsoft.com/jimgries/2007/07/06/why-does-visual-studio-require-debugger-symbol-files-to-exactly-match-the-binary-files-that-they-were-built-with/)
65
+
> [!IMPORTANT]
66
+
> The debugger will load only a .pdb file for an executable file that exactly matches the .pdb file that was created when the executable was built (that is, the .pdb must be the original or a copy of the original .pdb file). For more information, see [Why does Visual Studio require debugger symbol files to exactly match the binary files that they were built with?](https://blogs.msdn.microsoft.com/jimgries/2007/07/06/why-does-visual-studio-require-debugger-symbol-files-to-exactly-match-the-binary-files-that-they-were-built-with/)
64
67
65
68
Each project type may have a different way of setting these options.
66
69
67
70
### Generate symbol files for a C#, ASP.NET, or Visual Basic project
68
71
69
-
For detailed information on project settings for debug configurations in C#, see [Project settings for a C# Debug configuration](../debugger/project-settings-for-csharp-debug-configurations.md). For Visual Basic, see [this topic](../debugger/project-settings-for-a-visual-basic-debug-configuration.md).
72
+
For detailed information on project settings for debug configurations in C# or Visual Basic, see [Project settings for a C# debug configuration](../debugger/project-settings-for-csharp-debug-configurations.md) or [Project settings for a Visual Basic debug configuration](../debugger/project-settings-for-a-visual-basic-debug-configuration.md).
70
73
71
-
1.Right-click the project in Solution Explorer and choose **Properties**.
74
+
1.In Solution Explorer, select the project.
72
75
73
-
2.Choose a**Release** or **Debug** build from the **Configuration** list.
2. Choose **Build**settings and then click the **Advanced**button.
78
+
3. In the side pane, choose **Build**(or **Compile**in Visual Basic).
76
79
77
-
In Visual Basic, you choose the **Compile**settings and the **Advanced Compile Options**button instead.
80
+
4.In the **Configuration**list, choose **Debug**or **Release**.
78
81
79
-
3. Choose **full**,**portable**, or **pdb_only** in the **Debugging information** list box (**Generate debug info** in Visual Basic).
82
+
5. Select the**Advanced** button (or the **Advanced Compile Options** button in Visual Basic).
80
83
81
-
The portable format is the most recent cross-platform format for .NET Core. For more information on options, see [Advanced Build Settings dialog box (C#)](../ide/reference/advanced-build-settings-dialog-box-csharp.md).
84
+
6. In the **Debugging information** list (or the **Generate debug info** list in Visual Basic), choose **Full**, **Pdb-only**, or **Portable**.
82
85
83
-
![Generate PDBs for builds in C#](../debugger/media/dbg_project_properties_pdb_csharp.png"GeneratePDBsForCSharp")
86
+
The portable format is the most recent cross-platform format for .NET Core. For more information on options, see [Advanced Build Settings dialog box (C#)](../ide/reference/advanced-build-settings-dialog-box-csharp.md).
84
87
85
-
4. Build your project.
88
+
![Generate PDBs for builds in C#](../debugger/media/dbg_project_properties_pdb_csharp.png"GeneratePDBsForCSharp")
86
89
87
-
The symbol file(s) get created in the same folder as the executable or the main output file.
90
+
7. Build your project.
91
+
92
+
The compiler creates the symbol file(s) in the same folder as the executable or the main output file.
88
93
89
94
### Generate symbol files for a C++ project
90
95
91
-
1. Right-click the project in Solution Explorer and choose **Properties**.
96
+
1. In Solution Explorer, select the project.
97
+
98
+
2. Select the **Properties** icon (or press **Alt+Enter**).
99
+
100
+
3. In the **Configuration** list, choose **Debug** or **Release**.
92
101
93
-
2. Choose a **Release** or **Debug** build from the **Configuration** list.
102
+
4. In the side pane, choose **Linker > Debugging**, then select options for **Generate Debug Info**.
94
103
95
-
2. Under **Linker > Debugging**, select desired options for **Generate Debug Info**.
104
+
For detailed information on project settings for debug configurations in C++, see [Project settings for a C++ debug configuration](../debugger/project-settings-for-a-cpp-debug-configuration.md).
96
105
97
-
For detailed information on project settings for debug configurations in C++, see [Project settings for a C++ Debug configuration](../debugger/project-settings-for-a-cpp-debug-configuration.md).
106
+
5. Configure options for **Generate Program Database Files**.
98
107
99
-
4. Configure options for Generate Program Database Files
108
+
In most C++ projects, the default value is `$(OutDir)$(TargetName).pdb`, which generates .pdb files in the output folder.
100
109
101
-
In most C++ projects, the default value is `$(OutDir)$(TargetName).pdb`, which generates .pdb files in the output folder.
110
+
![Generate PDBs for builds in C++](../debugger/media/dbg_project_properties_pdb_cplusplus.png"GeneratePDBsforCPlusPlus")
102
111
103
-
![Generate PDBs for builds in C++](../debugger/media/dbg_project_properties_pdb_cplusplus.png"GeneratePDBsforCPlusPlus")
112
+
6. Build your project.
104
113
105
-
5. Build your project.
114
+
The compiler creates the symbol file(s) in the same folder as the executable or the main output file.
106
115
107
-
The symbol file(s) get created in the same folder as the executable or the main output file.
108
-
109
-
## See Also
110
-
[Specify symbol (.pdb) files and source files in the Visua Studio debugger](../debugger/debugger-settings-and-preparation.md)
111
-
[Debugger Settings and Preparation](../debugger/debugger-settings-and-preparation.md)
112
-
[Project Settings for a C++ Debug Configuration](../debugger/project-settings-for-a-cpp-debug-configuration.md)
113
-
[Project Settings for C# Debug Configurations](../debugger/project-settings-for-csharp-debug-configurations.md)
114
-
[Project Settings for a Visual Basic Debug Configuration](../debugger/project-settings-for-a-visual-basic-debug-configuration.md)
115
-
[How to: Create and Edit Configurations](../ide/how-to-create-and-edit-configurations.md)
116
+
## <aname="see-also"></a>See also
117
+
118
+
[Specify symbol (.pdb) files and source files in the Visual Studio debugger](../debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md)<br/>
119
+
[Debugger settings and preparation](../debugger/debugger-settings-and-preparation.md)<br/>
120
+
[Project settings for a C++ debug configuration](../debugger/project-settings-for-a-cpp-debug-configuration.md)<br/>
121
+
[Project settings for a C# debug configuration](../debugger/project-settings-for-csharp-debug-configurations.md)<br/>
122
+
[Project settings for a Visual Basic debug configuration](../debugger/project-settings-for-a-visual-basic-debug-configuration.md)<br/>
123
+
[How to: Create and edit configurations](../ide/how-to-create-and-edit-configurations.md)
Copy file name to clipboardExpand all lines: docs/ide/talk-to-us.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Talk to us"
3
3
ms.custom: ""
4
-
ms.date: 02/19/2018
4
+
ms.date: 10/09/2018
5
5
ms.prod: visual-studio-dev15
6
6
ms.technology: vs-acquisition
7
7
ms.prod: visual-studio-dev15
@@ -18,19 +18,19 @@ ms.workload:
18
18
---
19
19
# Visual Studio product feedback
20
20
21
-
We're interested in your ideas for improving our products and documentation. We can't always respond personally, but we'll make sure that your feedback gets to the right person or team.
21
+
Talk to us! We're interested in your ideas for improving our products and documentation. We can't always respond personally, but we'll make sure that your feedback gets to the right person or team.
22
22
23
23
## I want to report a problem with Visual Studio
24
24
25
-
If you are running into issues using Visual Studio, such as crashes, sluggish performance, unexpected behavior, and so on, please report the problem to us by using the **Report a Problem** tool. Simply click the feedback icon next to **Quick Launch**, or choose **Help** > **Send Feedback** > **Report a Problem** from the menu bar. Visual Studio reports the problem to [Developer Community](https://developercommunity.visualstudio.com). For more information, see [How to report a problem with Visual Studio 2017](how-to-report-a-problem-with-visual-studio-2017.md).
25
+
If you experience problems with Visual Studio—such as crashes, sluggish performance, or unexpected behavior—let us know by using the **Report a Problem** tool. In Visual Studio, choose the feedback icon next to **Quick Launch**, or choose **Help** > **Send Feedback** > **Report a Problem** from the menu bar. Next, Visual Studio opens the [Developer Community](https://developercommunity.visualstudio.com) page in your browser, where you can sign in to report the problem. For more information, see [How to report a problem with Visual Studio 2017](how-to-report-a-problem-with-visual-studio-2017.md).
26
26
27
27
## I want to make a suggestion about Visual Studio features
28
28
29
-
If there's something we can do better, please let us know! Choose **Help** > **Send Feedback** > **Provide a Suggestion**to suggest a feature or change to the Visual Studio team. Your suggestion will automatically be posted to [UserVoice](https://visualstudio.uservoice.com), where others can up-vote it.
29
+
If there's something we can do better, tell us about it! In Visual Studio, choose **Help** > **Send Feedback** > **Provide a Suggestion**from the menu bar. Next, Visual Studio opens the [Developer Community](https://developercommunity.visualstudio.com) page in your browser, where you can sign in to share your idea. For more information, see [Suggest a feature for Visual Studio 2017](suggest-a-feature.md).
30
30
31
31
### Rate this product
32
32
33
-
Pre-release versions of Visual Studio have a **Rate this Product** menu item that enables you to send feedback on the quality of the build you are running. You won't see this in released versions of the product.
33
+
Pre-release versions of Visual Studio have a **Rate this Product** menu item that released versions of the product don't have. Use the **Rate this Product** menu item to send feedback on the quality of the pre-release build that you're running.
34
34
35
35
## I want to contact Microsoft Support
36
36
@@ -45,11 +45,11 @@ For larger organizations that require managed support directly from Microsoft, c
45
45
46
46
If the product came installed with a new computer or device, the hardware manufacturer provides technical support and assistance for this software. Contact the manufacturer directly for support.
47
47
48
-
Microsoft support services are subject to then-current prices, terms, and conditions. Prices, terms, and conditions are subject to change without notice.
48
+
Microsoft support services are subject to then-current prices, terms, and conditions. Prices, terms, and conditions can change without notice.
49
49
50
50
## I want to get involved in the developer community
51
51
52
-
If you want to share your questions and answers with other developers, you can use the [Visual Studio Developer Community](https://developercommunity.visualstudio.com) site, the [MSDN forums](http://social.msdn.microsoft.com/Forums/home), or [StackOverflow](http://stackoverflow.com/). You can also view code from other developers and share your own examples on the [Developer code samples](http://code.msdn.microsoft.com/) site.
52
+
If you want to share your questions and answers with other developers, use the [Visual Studio Developer Community](https://developercommunity.visualstudio.com) site, the [MSDN forums](http://social.msdn.microsoft.com/Forums/home), or [StackOverflow](http://stackoverflow.com/). You can also view code from other developers and share your own examples on the [Developer code samples](http://code.msdn.microsoft.com/) site.
53
53
54
54
## I want to help improve the Visual Studio documentation
Copy file name to clipboardExpand all lines: docs/install/includes/install_get_support_md.md
+2-3Lines changed: 2 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,5 @@ We also offer a [**live chat**](https://visualstudio.microsoft.com/vs/support/#t
10
10
Here are a few more support options:
11
11
12
12
* Report product issues to us via the [Report a Problem](../../ide/how-to-report-a-problem-with-visual-studio-2017.md) tool that appears both in the Visual Studio Installer and in the Visual Studio IDE.
13
-
* Share a product suggestion with us on [UserVoice](https://visualstudio.uservoice.com/forums/121579).
14
-
* Track product issues and find answers in the [Visual Studio Developer Community](https://developercommunity.visualstudio.com/).
15
-
* Use your [GitHub](https://github.com/) account to talk to us and other Visual Studio developers in the [Visual Studio conversation in the Gitter community](https://gitter.im/Microsoft/VisualStudio).
13
+
* Suggest a feature, track product issues, and find answers in the [Visual Studio Developer Community](https://developercommunity.visualstudio.com/).
14
+
* Use your [GitHub](https://github.com/) account to talk to us and other Visual Studio developers in the [Visual Studio conversation in the Gitter community](https://gitter.im/Microsoft/VisualStudio).
0 commit comments