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
Copy file name to clipboardExpand all lines: docs/ai/create-project-existing.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -29,4 +29,4 @@ Once you've [installed Visual Studio Tools for AI](installation.md), it's easy t
29
29
30
30
## See Also
31
31
32
-
-[Creating an environment for an existing Python interpreter](../python/managing-python-environments-in-visual-studio.md#creating-an-environment-for-an-existing-interpreter)
32
+
-[Manually identifying an existing Python environment](../python/managing-python-environments-in-visual-studio.md#manually-identifying-an-existing-environment)
Copy file name to clipboardExpand all lines: docs/ai/create-project-repo.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ Once you've [installed Visual Studio Tools for AI](installation.md), you can eas
36
36
37
37

38
38
39
-
> If you are using Anaconda and get an error about missing numpy, you may need to change your python environment you may need to [change your python environment to use Anaconda](../python/managing-python-environments-in-visual-studio.md)
39
+
> If you are using Anaconda and get an error about missing numpy, you may need to [change your Python environment to use Anaconda](../python/selecting-a-python-environment-for-a-project.md).
40
40
41
41
11. You can visualize the progress with TensorBoard. Right click your project and click **Run TensorBoard** then select the directory of your output TensorBoard logs.
Copy file name to clipboardExpand all lines: docs/code-quality/how-to-configure-code-analysis-for-an-aspnet-web-application.md
-2Lines changed: 0 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -20,8 +20,6 @@ ms.workload:
20
20
21
21
In Visual Studio, you can select from a list of Code Analysis *rule sets* to apply to [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] Web application. The default rule set is the Microsoft Minimum Recommended Rules. You can select another rule set to apply to the Web site.
22
22
23
-
## To configure a rule set for an ASP.NET Page Framework project
24
-
25
23
1. Select the Web site in **Solution Explorer**.
26
24
27
25
2. On the **Analyze** menu, click **Configure Code Analysis for Web Site**.
Copy file name to clipboardExpand all lines: docs/debugger/debugging-managed-code.md
+66-65Lines changed: 66 additions & 65 deletions
Original file line number
Diff line number
Diff line change
@@ -17,75 +17,76 @@ helpviewer_keywords:
17
17
- "debugging managed code"
18
18
- "debugging ASP.NET Web applications, managed code"
19
19
- "managed code, debugging"
20
-
ms.assetid: fa3aff01-c271-4aa7-b5b1-def560471c84
21
-
caps.latest.revision: 34
22
20
author: "mikejo5000"
23
21
ms.author: "mikejo"
24
22
manager: ghogen
25
23
ms.workload:
26
24
- "dotnet"
27
25
---
28
26
# Debugging Managed Code
29
-
This section covers common debugging problems and techniques for managed applications, or applications written in languages that target the common language runtime, such as Visual Basic, C#, and C++. The techniques described here are high-level techniques. For more information, see [Using the Debugger](../debugger/debugger-basics.md).
30
-
31
-
## In This Section
32
-
[Diagnostic Messages in the Output Window](../debugger/diagnostic-messages-in-the-output-window.md)
33
-
Describes the <xref:System.Diagnostics.Debug> and <xref:System.Diagnostics.Trace> classes, with which you can write run-time messages to the **Output** window. These classes include output methods that enable information output without breaking execution and information output that also breaks execution if a specified condition fails.
34
-
35
-
[Assertions in Managed Code](../debugger/assertions-in-managed-code.md)
36
-
Describes assertions in managed code, which test conditions that you specify as arguments to `Assert` methods. In addition, this topic provides example code, information on using <xref:System.Diagnostics.Debug> and <xref:System.Diagnostics.Trace> class methods, considerations in Debug and Release versions of code, side effects, assert arguments, customizing assert behavior, and configuration files.
37
-
38
-
[Stop Statements in Visual Basic](../debugger/stop-statements-in-visual-basic.md)
39
-
Describes the `Stop` statement, which provides an alternative to setting a breakpoint. Example code is also provided, along with comparisons between the `Stop` statement and the `End` statement, as well as between `Stop` and the `Assert` statement.
40
-
41
-
[Walkthrough: Debugging a Windows Form](../debugger/walkthrough-debugging-a-windows-form.md)
42
-
Gives step-by-step instructions for creating a Windows Form and debugging that form. A Windows Form, a standard component of a managed Windows application, is one of the most common managed applications. This walkthrough uses Visual C# and Visual Basic, but the techniques for creating a Windows form with C++ are generally similar.
43
-
44
-
[Debugging the OnStart Method](../debugger/how-to-debug-the-onstart-method.md)
45
-
Provides code examples to allow you to debug the `OnStart` method of a managed Windows service. To debug the `OnStart` method of a Windows service, you must add a few lines of code to simulate the service.
Discusses debugging mixed-mode applications. This means any application that combines native code with managed code.
49
-
50
-
[Error: Debugging isn't possible because a kernel debugger is enabled on the system](../debugger/error-debugging-isn-t-possible-because-a-kernel-debugger-is-enabled-on-the-system.md)
51
-
Describes an error message that occurs if you try to debug managed code on a [!INCLUDE[win7](../debugger/includes/win7_md.md)], [!INCLUDE[wiprlhext](../debugger/includes/wiprlhext_md.md)], [!INCLUDE[winxp](../code-quality/includes/winxp_md.md)], [!INCLUDE[Win2kFamily](../code-quality/includes/win2kfamily_md.md)], or Windows NT system that has been started in debug mode.
52
-
53
-
[JIT Optimization and Debugging](../debugger/jit-optimization-and-debugging.md)
54
-
Describes the effects of JIT optimization on debugging.
55
-
56
-
[Debugging LINQ and DLINQ](../debugger/debugging-linq.md)
57
-
Discusses techniques for debugging LINQ queries.
58
-
59
-
[Walkthrough: Debugging a Parallel Application](../debugger/walkthrough-debugging-a-parallel-application.md)
60
-
Describes how to use the **Parallel Tasks** and **Parallel Stacks** tool windows to debug a parallel application.
61
-
62
-
## Related Sections
63
-
[IntelliTrace](../debugger/intellitrace.md)
64
-
Find bugs faster and easier by recording your app's execution history with IntelliTrace. Step backward and forward through recorded events and calls to examine your app's state at key points in time. Debug your code without setting lots of breakpoints or restarting your app as frequently. Requires Visual Studio Ultimate.
65
-
66
-
[Tracing and Instrumenting Applications](/dotnet/framework/debug-trace-profile/tracing-and-instrumenting-applications)
67
-
Describes tracing, a way for you to monitor the execution of your application while it is running, and instrumenting, which involves placing trace statements at strategic locations in your code. This topic also provides links to an introduction to instrumentation and tracing, trace switches, trace listeners, tracing code in an application, adding trace statements to application code, and compiling conditionally with <xref:System.Diagnostics.Debug> and <xref:System.Diagnostics.Trace>.
Describes a linker option that adds <xref:System.Diagnostics.DebuggableAttribute> to code written with C++. This attribute is needed to use debugging features such as attach with C++.
71
-
72
-
[Debugging Windows Service Applications](/dotnet/framework/windows-services/how-to-debug-windows-service-applications)
73
-
Provides considerations for debugging Windows service applications, including setting up, attaching to the process, debugging the code in the service's `OnStart` method and the code in the Main method, setting breakpoints, and using the Services Control Manager to start, stop, pause, and continue your service.
74
-
75
-
[Debugging and Profiling](/dotnet/framework/debug-trace-profile/index)
76
-
Discusses debugging .NET Framework applications and the configuration requirements.
77
-
78
-
[Debugging Script and Web Applications](../debugger/debugging-web-applications-and-script.md)
79
-
Describes common debugging problems and techniques you may encounter when debugging script and Web applications.
80
-
81
-
[What's New for the Debugger in Visual Studio 2015](../debugger/what-s-new-for-the-debugger-in-visual-studio.md)
82
-
Description of new debugging features added in this release of [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)].
83
-
84
-
[Debugging Home Page](../debugger/debugger-feature-tour.md)
85
-
Provides links to the larger sections of the debugging documentation. Information includes what's new in the debugger, settings and preparation, breakpoints, handling exceptions, edit and continue, debugging managed code, debugging Visual C++ projects, debugging COM and ActiveX, debugging DLLs, debugging SQL, and the user interface references.
86
-
87
-
## See Also
88
-
[Walkthrough: Debugging Custom Windows Forms Controls at Design Time](/dotnet/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time)
This section covers common debugging problems and techniques for managed applications, or applications written in languages that target the common language runtime, such as Visual Basic, C#, and C++. The techniques described here are high-level techniques. For more information, see [Using the Debugger](../debugger/debugger-basics.md).
29
+
30
+
## In This Section
31
+
32
+
[Diagnostic Messages in the Output Window](../debugger/diagnostic-messages-in-the-output-window.md)
33
+
Describes the <xref:System.Diagnostics.Debug> and <xref:System.Diagnostics.Trace> classes, with which you can write run-time messages to the **Output** window. These classes include output methods that enable information output without breaking execution and information output that also breaks execution if a specified condition fails.
34
+
35
+
[Assertions in Managed Code](../debugger/assertions-in-managed-code.md)
36
+
Describes assertions in managed code, which test conditions that you specify as arguments to `Assert` methods. In addition, this topic provides example code, information on using <xref:System.Diagnostics.Debug> and <xref:System.Diagnostics.Trace> class methods, considerations in Debug and Release versions of code, side effects, assert arguments, customizing assert behavior, and configuration files.
37
+
38
+
[Stop Statements in Visual Basic](../debugger/stop-statements-in-visual-basic.md)
39
+
Describes the `Stop` statement, which provides an alternative to setting a breakpoint. Example code is also provided, along with comparisons between the `Stop` statement and the `End` statement, as well as between `Stop` and the `Assert` statement.
40
+
41
+
[Walkthrough: Debugging a Windows Form](../debugger/walkthrough-debugging-a-windows-form.md)
42
+
Gives step-by-step instructions for creating a Windows Form and debugging that form. A Windows Form, a standard component of a managed Windows application, is one of the most common managed applications. This walkthrough uses Visual C# and Visual Basic, but the techniques for creating a Windows form with C++ are generally similar.
43
+
44
+
[Debugging the OnStart Method](../debugger/how-to-debug-the-onstart-method.md)
45
+
Provides code examples to allow you to debug the `OnStart` method of a managed Windows service. To debug the `OnStart` method of a Windows service, you must add a few lines of code to simulate the service.
Discusses debugging mixed-mode applications. This means any application that combines native code with managed code.
49
+
50
+
[Error: Debugging isn't possible because a kernel debugger is enabled on the system](../debugger/error-debugging-isn-t-possible-because-a-kernel-debugger-is-enabled-on-the-system.md)
51
+
Describes an error message that occurs if you try to debug managed code on a [!INCLUDE[win7](../debugger/includes/win7_md.md)], [!INCLUDE[wiprlhext](../debugger/includes/wiprlhext_md.md)], [!INCLUDE[winxp](../code-quality/includes/winxp_md.md)], [!INCLUDE[Win2kFamily](../code-quality/includes/win2kfamily_md.md)], or Windows NT system that has been started in debug mode.
52
+
53
+
[JIT Optimization and Debugging](../debugger/jit-optimization-and-debugging.md)
54
+
Describes the effects of JIT optimization on debugging.
55
+
56
+
[Debugging LINQ and DLINQ](../debugger/debugging-linq.md)
57
+
Discusses techniques for debugging LINQ queries.
58
+
59
+
[Walkthrough: Debugging a Parallel Application](../debugger/walkthrough-debugging-a-parallel-application.md)
60
+
Describes how to use the **Parallel Tasks** and **Parallel Stacks** tool windows to debug a parallel application.
61
+
62
+
## Related Sections
63
+
64
+
[IntelliTrace](../debugger/intellitrace.md) Find bugs faster and easier by recording your app's execution history with IntelliTrace. Step backward and forward through recorded events and calls to examine your app's state at key points in time. Debug your code without setting lots of breakpoints or restarting your app as frequently. Requires Visual Studio Enterprise.
65
+
66
+
[Tracing and Instrumenting Applications](/dotnet/framework/debug-trace-profile/tracing-and-instrumenting-applications)
67
+
Describes tracing, a way for you to monitor the execution of your application while it is running, and instrumenting, which involves placing trace statements at strategic locations in your code. This topic also provides links to an introduction to instrumentation and tracing, trace switches, trace listeners, tracing code in an application, adding trace statements to application code, and compiling conditionally with <xref:System.Diagnostics.Debug> and <xref:System.Diagnostics.Trace>.
Describes a linker option that adds <xref:System.Diagnostics.DebuggableAttribute> to code written with C++. This attribute is needed to use debugging features such as attach with C++.
71
+
72
+
[Debugging Windows Service Applications](/dotnet/framework/windows-services/how-to-debug-windows-service-applications)
73
+
Provides considerations for debugging Windows service applications, including setting up, attaching to the process, debugging the code in the service's `OnStart` method and the code in the Main method, setting breakpoints, and using the Services Control Manager to start, stop, pause, and continue your service.
74
+
75
+
[Debugging and Profiling](/dotnet/framework/debug-trace-profile/index)
76
+
Discusses debugging .NET Framework applications and the configuration requirements.
77
+
78
+
[Debugging Script and Web Applications](../debugger/debugging-web-applications-and-script.md)
79
+
Describes common debugging problems and techniques you may encounter when debugging script and Web applications.
80
+
81
+
[What's New for the Debugger in Visual Studio 2015](../debugger/what-s-new-for-the-debugger-in-visual-studio.md)
82
+
Description of new debugging features added in this release of [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)].
83
+
84
+
[Debugging Home Page](../debugger/debugger-feature-tour.md)
85
+
Provides links to the larger sections of the debugging documentation. Information includes what's new in the debugger, settings and preparation, breakpoints, handling exceptions, edit and continue, debugging managed code, debugging Visual C++ projects, debugging COM and ActiveX, debugging DLLs, debugging SQL, and the user interface references.
86
+
87
+
## See also
88
+
89
+
[Walkthrough: Debugging Custom Windows Forms Controls at Design Time](/dotnet/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time)
0 commit comments