Project Settings for a Visual Basic Debug Configuration
You can change the project settings for a Visual Basic debug configuration in the Property Pages window, as discussed in Debug and Release Configurations. The following tables show where to find debugger-related settings in the Property Pages window.
This topic does not apply to UWP apps. See Start a debug session (VB, C#, C++ and XAML)
|Configuration||Sets mode for compiling the application. Choose among Active (Debug), Debug, Release, All Configurations.|
|Start Action||This group of controls specifies the action that will occur when you choose Start from the Debug menu.
- Start project is the default and launches the startup project for debugging.
- Start external program enables you to start and attach to a program that is not part of a Visual Studio project. For more information, see Attach to Running Processes.
- Start browser in URL enables you to debug a Web application.
|Command Line Arguments||Specifies command-line arguments for the program to be debugged. The command name is the program name specified in Start external program. If Start Action is set to Start URL, command-line arguments are ignored.|
|Working Directory||Specifies the working directory of the program being debugged. In Visual Basic, the working directory is the directory the application is launched from. The default working directory is \bin\Debug or \bin\Release, depending on the current configuration.|
|Use Remote Machine||When the check box is selected, remote debugging is enabled. In the textbox, you can type name of a remote machine where the application will run for debugging purposes or an Msvsmon server name. The location of the EXE on the remote machine is specified by the Output Path property in the Build tab. The location must be a shareable directory on the remote machine.|
|Unmanaged code debugging||Enables you to debug calls to native (unmanaged) Win32 code from your managed application. This has the same effect as selecting Mixed for Debugger Type in a Visual C++ project.|
|SQL Server debugging||Allows debugging of SQL Server database objects.|
Compile tab: press Advanced Compile Options button
|Enable optimizations||This option should be unchecked. Optimization causes the code that is actually executed to be different from the source code seen in Visual Studio, and thus makes debugging difficult. If code is optimized, symbols are not be loaded by default when debugging with Just My Code.|
|Generate debug info||Defined by default in both debug and release versions, this setting (equivalent to the /debug compiler option) creates debug information at build time. The debugger uses this information to show variable names and other information in a useful form when you are debugging. If you compile your program without this information, debugger functionality will be limited. For more information, see /debug.|
|Define DEBUG Constant||Defining this symbol enables conditional compiling of output functions from the Debug class. With this symbol defined, Debug class methods generate output to the Output window. Without this symbol, Debug class methods are not compiled and no output is generated. This symbol should be defined in the Debug version and not defined in the Release version. Defining this symbol in a Release version creates unnecessary code that slows your program down.|
|Define TRACE Constant||Defining this symbol enables conditional compiling of output functions from the Trace class. With this symbol defined, the Trace class methods generate output to the Output window. Without this symbol, Trace class methods are not compiled and no Trace output is generated. This symbol is defined by default for both Debug and Release versions.|