Use the Visual Studio debugger to quickly find and fix bugs across languages. The Visual Studio for Mac debugger lets you step inside your code by setting Breakpoints, Step Over statements, Step Into and Out of functions, and inspect the current state of the code stack through powerful visualizations.
- Download Visual Studio Code On Chromebook
- Download Visual Studio Code Para Mac
- Visual Studio Code For Beginners
Developer Community |System Requirements |Compatibility |Distributable Code |Documentation |Blogs |Servicing
Download and install Visual Studio Code Download Visual Studio Cod It is NOT Visual Studio 2017; 2. Click on zip archive and you’ll see VS Code logo. Click on it and you’ll see VS Code opened. Then do the following setup: Open VSC. Go to Code – Preferences – Extensions. General Add selection to next Find match ⇧⌘P, F1 Show Command Palette ⌘P Quick Open, Go to File ⇧⌘N New window/instance ⌘W ⌘Close window/instance.
Click the button to download the latest version of Visual Studio 2019 for Mac. For information on the system requirements see the see Mac System Requirementsand Mac Platform Targeting and Compatibility guides.
Download Visual Studio Code On Chromebook
For instructions on installing and updating Visual Studio 2019 for Mac, see theInstall Visual Studio for Mac guide.
To learn more about other related downloads, see the Downloads page.
What's New in Visual Studio 2019 for Mac
Visual Studio 2019 for Mac Releases
- April 21, 2021 - Visual Studio 2019 for Mac version 8.9.7
- April 13, 2021 - Visual Studio 2019 for Mac version 8.9.6
- April 6, 2021 - Visual Studio 2019 for Mac version 8.9.5
- March 30, 2021 - Visual Studio 2019 for Mac version 8.9.4
- March 23, 2021 - Visual Studio 2019 for Mac version 8.9.3
- March 16, 2021 - Visual Studio 2019 for Mac version 8.9.2
- March 9, 2021 - Visual Studio 2019 for Mac version 8.9.1
- March 2, 2021 - Visual Studio 2019 for Mac version 8.9
Visual Studio 2019 for Mac Blog Posts
The Visual Studio Blog is the official source of product insight from the Visual Studio Engineering Team. You can find in-depth information about the Visual Studio 2019 for Mac releases in the following posts:
Release Highlights
- Visual Studio for Mac 8.9 introduces a new native XML editor.
- Visual Studio for Mac 8.9 uses the native editor inside the Immediate window.
- Visual Studio for Mac 8.9 introduces support for Solution Filter (*.slnf) files.
- Visual Studio for Mac 8.9 introduces a new Git Blame view using the native editor.
- Visual Studio for Mac 8.9 adds a new Quick Actions and Refactoring experience as a preview feature (Preview features can be enabled in Preferences > Other > Preview Features).
- Visual Studio for Mac 8.9 adds support for filtering first chance exceptions by type, module, and function location as a preview feature (Preview features can be enabled in Preferences > Other > Preview Features).
- Visual Studio for Mac 8.9 has full accessibility support enabled by default.
- Visual Studio for Mac 8.9 no longer includes the iOS designer.
- Visual Studio for Mac 8.9 no longer includes the Xamarin.Forms previewer in favor of XAML Hot Reload. For more info see https://aka.ms/xamlhotreload.
- Visual Studio for Mac 8.9 introduces support for version 30 of the Android SDK API.
- Visual Studio for Mac 8.9 adds support for running and debugging unit tests for Unity projects.
- Visual Studio for Mac 8.9 improves the Locals tool window for Unity projects.
Known Issues
Refer to the Known Issues section.
Feedback and Suggestions
We would love to hear from you! You can report a problem through the Report a Problem option in Visual Studio for Mac IDE.You can track your feedback, including suggestions, in the Developer Community portal.
Release Notes
Visual Studio 2019 for Mac version 8.9.7 (8.9.7.8)
released April 21, 2021
General
- We fixed a couple reliability issues in the Xamarin and Unity experiences.
Debugger
- We fixed an issue where the 'Enable subprocess debugging' option wasn't working correctly.
Version Control
- We fixed an issue where the scroll position was not in sync between the editor and the blame view.
Visual Studio 2019 for Mac version 8.9.6 (8.9.6.6)
released April 13, 2021
General
- We fixed several reliability issues.
Web and Azure
- We updated .NET Core SDKs to 5.0.202 and 3.1.408.
Tools for Unity
- We fixed a possible crash when retrieving unit tests from the Unity Editor.
Visual Studio 2019 for Mac version 8.9.5 (8.9.5.4)
released April 6, 2021
General
- We fixed several reliability issues.
Visual Studio 2019 for Mac version 8.9.4 (8.9.4.25)
released March 30, 2021
General
- We fixed several reliability and performance issues.
Source Code Editing
- We fixed an issue where Cmd+Click was hard to use / flickering.
Version Control
- We fixed an issue where the editor was read only after using the Git Blame.
Visual Studio 2019 for Mac version 8.9.3 (8.9.3.13)
released March 23, 2021
General
- We fixed several reliability and performance issues.
Web and Azure
- We fixed an issue where preprocessed Razor pages were missing or not precompiled.
Visual Studio 2019 for Mac version 8.9.2 (8.9.2.0)
released March 16, 2021
General
- We fixed several reliability and performance issues.
Version Control
- We fixed an issue where the commit dialog was showing duplicated tooltips
Xamarin
- We fixed an issue where VS for Mac couldn't find Xcode.
- We fixed an issue where [building Android projects failed if the Android SDK was missing].
Visual Studio 2019 for Mac version 8.9.1 (8.9.1.34)
released March 9, 2021
General
- We fixed several reliability and performance issues.
Source Code Editing
- We fixed an issue where it was not possible to go to definition using CMD+Click.
Web and Azure
- We updated the roslyn compiler to address several issues with Blazor and .NET 6.
- We updated .NET Core SDKs to 5.0.201 and 3.1.407 addressing CVE-2021-26701
Tools for Unity
- We fixed an issue where canceling a running test was not working correctly.
Visual Studio 2019 for Mac version 8.9 (8.9.0.1651)
released March 2, 2021
New Features
Project System
- We added support for Solution Filter (*.slnf) files.
Web and Azure
- We added support for .NET 6 workloads and projects.
Tools for Unity
- Added support for running and debugging Unity tests in VS for Mac
- Added
Active Scene
to locals, showing root game objects. - Added
this.gameObject
to locals, given it's widely used in Unity projects. - Added
Children
andComponents
groups to allGameObject
instances, so that you can easily display all the object hierarchy. - Added
Scene Path
to allGameObject
instances, to show the location in the scene. - Added support for
JobEntityBatch
/Lambdas when using Entities with source generators. - Improved support for displaying large arrays (using index bucketing).
- Added support for
raytrace shaders
,UXML
andUSS
files. - Updated Unity messages API (for all methods used as coroutines).
- Updated Android SDK detection.
Bug Fixes
General
- We fixed a critical crash reporting issue.
- We fixed several issues with reliability and performance.
- We updated Mono to 6.12.0.122 addressing CVE-2021-24112
Debugger
- We fixed an issue blocking operations when multiple watches are selected in the watch tool window.
- We fixed several issues causing the wrong value to be copied or pasted within the watch tool window.
- We fixed an issue where it was not possible to rename a watch while debugging.
- We fixed an issue where it was not possible to debug 32 bit assemblies using Run > Debug Application.
- We fixed an issue where the Exception window appears outside of the desktop.
- We fixed an issue where the Set Next Statement command failed with an error depending on where the editor caret was placed.
- We fixed an issue where catchpoints didn't work with .NET Core.
- We fixed an issue where Debugging was not working with XCode 12.
Project System
- We fixed an issue where a new project configuration added on VS 2017 on Windows does not load properly on VS for Mac.
- We fixed an issue that could cause the solution tree to be blank under certain conditions.
- We fixed an issue where a changed Xamarin.Forms project was not rebuilt upon deployment.
- We fixed an issue where the evaluation of complex ProjectReference conditions failed.
- We fixed an issue where moving or renaming nested files didn't work.
Installer
- We updated the Android SDK API version to 30.
- We fixed an issue where downloading the .NET Core package failed.
Shell and Tools
- We increased the speed of the find in files functionality.
- We fixed an issue where saving failed after excluding resources from a project.
- We fixed a potential accessibility issue where the color contrast of the integrated terminal's selection color in dark mode is too low.
- We fixed an issue where loading a solution failed after closing VS for Mac in full screen mode on Big Sur.
- We fixed an issue where the Welcome screen close button was invisible on macOS Big Sur.
- We fixed an issue where it was not possible to type special characters in the terminal tool window while pressing the option key.
- We fixed an issue where the build output was shown instead of the error window when clicking on an error inside the status bar.
- We fixed an issue where alerts were not clickable with the mouse on macOS Big Sur.
- We fixed an issue where the Errors tool window didn't remember toolbar button settings.
- We fixed an issue where searching for 'Problems and Solutions' failed sometimes.
- We fixed an issue where the 'Show Start Window' menu item was missing.
- We fixed an issue where it was not possible to restart a project without debugging.
Source Code Editing
- We fixed an issue where F# 4.6 language features don't work on VS for Mac (Stable or Preview).
- We fixed an issue where member _.method in F # was not recognized correctly.
- We fixed build issues with new F# Web projects.
- We fixed an issue where Find References is not working.
- We fixed an issue with the Rename functionality not working correctly.
- We fixed an issue where Extension Methods navigation search operation was running indefinitely.
- We fixed an issue with missing support for FSharp.Core 4.7.
- We fixed various issues with GB18030 encoding support.
- We fixed an issue where a custom key binding for the Find Caret command was not working in the new editor.
- We fixed an issue where Find References is not working.
- We fixed an issue with the Rename functionality not working correctly.
- We fixed an issue with YAML support.
- We fixed an issue with orphaned Quick Action popups.
- We fixed an issue where IntelliSense stopped functioning in a C# project referencing another F# project.
- We fixed an issue with a low text contrast in lines with a breakpoint.
Test Tools
- We fixed an issue where Running unit tests from the context menu was way slower than from the Unit Tests pad.
Version Control
- We improved the Blame view and made it more accessible.
- We fixed an issue where switching branches got stuck at 'Updating version control repository'.
- We fixed an issue where Visual Studio Mac won't recognize the latest updates to the code.
- We fixed an issue where an error was shown after copying a file if Git was not installed.
- We fixed an issue where deleting a new file under a newly added folder deleted the empty folder as well.
- We fixed an issue where 'Publishing Project' never completed.
- We fixed an issue with where the alert about missing Xcode command line tools was too intrusive.
- We fixed an issue where stashing failed with an error.
Web and Azure
- We updated .NET Core SDKs to 5.0.103 and 3.1.406.
- We fixed an issue where IntelliSense shows the OpenAPI client after the OpenAPI service was removed.
- We fixed an issue where incorrect ASPNETCORE_URLS environment variable was generated when debugging apps.
- We fixed several issues where dynamic parameters were not loaded correctly from some custom templates.
- We fixed an issue where loading Blazor Web Assembly projects failed if the project path contained spaces.
- We fixed an issue where publishing ASP.NET Core 5.0 projects to Azure failed with an 'HTTP Error 500.31 - ANCM Failed to Find Native Dependencies' error.
- We fixed an issue with debugging Azure Functions locally.
Tools for Unity
- Fixed search highlighting in Unity message dialog.
- Fixed stability issues with Unity project treeview.
- Fixed handling of conditional breakpoints.
- Fixed stability issues with Unity message dialog
- Fixed various UI issues for non ENU languages.
- Fixed stability issues with
UNT0018
diagnostic. - Fixed VM disconnection issues when using
Trace
methods. - Fixed filtering of obsolete properties throwing exceptions.
- Fixed
UNT0006
diagnostic, giving wrong warnings for Coroutines andAssetPostprocessor.OnAssignMaterialModel
. - Added missing Unity messages for 2019.4 API.
Xamarin
- We added support for Xcode 12.4.
- The iOS designer is no longer part of Visual Studio for Mac. We have made improvements to our Xcode sync process to help you adapt to using Xcode to design your Xamarin.iOS storyboards. See Designing user interfaces with Xcode - Xamarin | Microsoft Docs to learn more.
- The Xamarin.Forms previewer is being removed in favor of XAML Hot Reload. For more info see https://aka.ms/xamlhotreload.
- We fixed an issue where Xamarin project files were always shown as edited in git.
Known Issues
The following is a list of all existing known issues in Visual Studio 2019 for Mac version 8.9:
- After installing the latest .NET 5 SDK, developers of .NET Core 3.1 apps might see an error indicating 'The ASP.NET Core developer certificate is in an invalid state.'. Running
dotnet dev-certs https --clean
thendotnet dev-certs https --trust
from the Terminal will fix the issue. - In rare cases, it's possible to be up to date with everything but the .NET Core 3.1.300 SDK. If you enter into this configuration and update to .NET Core 3.1.300 using the updater, the notification to update the .NET Core SDK will not disappear until the IDE is restarted.
- If you're already on Big Sur and can't use the updater, visit the Visual Studio for Mac website and download the installer.
- On Big Sur gRPC projects may fail to build with an error
protoc' exited with code 255
. This is a problem with macOS platform detection in the gRPC.Tools NuGet package that is used by default in the project templates. A workaround is to update the gRPC.Tools NuGet package to version 2.34.0 or later.
In this tutorial, you configure Visual Studio Code on macOS to use the Clang/LLVM compiler and debugger.
After configuring VS Code, you will compile and debug a simple C++ program in VS Code. This tutorial does not teach you about Clang or the C++ language. For those subjects, there are many good resources available on the Web.
If you have any trouble, feel free to file an issue for this tutorial in the VS Code documentation repository.
Prerequisites
To successfully complete this tutorial, you must do the following:
- Install Visual Studio Code on macOS.
- Install the C++ extension for VS Code. You can install the C/C++ extension by searching for 'c++' in the Extensions view (⇧⌘X (Windows, Linux Ctrl+Shift+X)).
Ensure Clang is installed
Clang may already be installed on your Mac. To verify that it is, open a macOS Terminal window and enter the following command:
- If Clang isn't installed, enter the following command to install the command line developer tools:
Create Hello World
From the macOS Terminal, create an empty folder called
projects
where you can store all your VS Code projects, then create a subfolder called helloworld
, navigate into it, and open VS Code in that folder by entering the following commands:The
code .
command opens VS Code in the current working folder, which becomes your 'workspace'. As you go through the tutorial, you will create three files in a .vscode
folder in the workspace:tasks.json
(compiler build settings)launch.json
(debugger settings)c_cpp_properties.json
(compiler path and IntelliSense settings)
Add hello world source code file
In the File Explorer title bar, select New File and name the file
helloworld.cpp
.Paste in the following source code:
Now press ⌘S (Windows, Linux Ctrl+S) to save the file. Notice that your files are listed in the File Explorer view (⇧⌘E (Windows, Linux Ctrl+Shift+E)) in the side bar of VS Code:
You can also enable Auto Save to automatically save your file changes, by checking Auto Save in the main File menu.
The Activity Bar on the edge of Visual Studio Code lets you open different views such as Search, Source Control, and Run. You'll look at the Run view later in this tutorial. You can find out more about the other views in the VS Code User Interface documentation.
Note: When you save or open a C++ file, you may see a notification from the C/C++ extension about the availability of an Insiders version, which lets you test new features and fixes. You can ignore this notification by selecting the
X
(Clear Notification).Explore IntelliSense
In the
helloworld.cpp
file, hover over vector
or string
to see type information. After the declaration of the msg
variable, start typing msg.
as you would when calling a member function. You should immediately see a completion list that shows all the member functions, and a window that shows the type information for the msg
object:You can press the Tab key to insert the selected member. Then, when you add the opening parenthesis, you'll see information about arguments that the function requires.
Build helloworld.cpp
Next, you'll create a
tasks.json
file to tell VS Code how to build (compile) the program. This task will invoke the Clang C++ compiler to create an executable file from the source code.It's important to have
helloworld.cpp
open in the editor because the next step uses the active file in the editor as context to create the build task in the next step.From the main menu, choose Terminal > Configure Default Build Task. A dropdown will appear listing various predefined build tasks for the compilers that VS Code found on your machine. Choose C/C++ clang++ build active file to build the file that is currently displayed (active) in the editor.
This will create a
tasks.json
file in the .vscode
folder and open it in the editor.Replace the contents of that file with the following:
The JSON above differs from the default template JSON in the following ways:
'args'
is updated to compile with C++17 because ourhelloworld.cpp
uses C++17 language features.- Changes the current working directory directive (
'cwd'
) to the folder wherehelloworld.cpp
is.
The
command
setting specifies the program to run. In this case, 'clang++'
is the driver that causes the Clang compiler to expect C++ code and link against the C++ standard library.The
args
array specifies the command-line arguments that will be passed to clang++. These arguments must be specified in the order expected by the compiler.This task tells the C++ compiler to compile the active file (
${file}
), and create an output file (-o
switch) in the current directory (${fileDirname}
) with the same name as the active file (${fileBasenameNoExtension}
), resulting in helloworld
for our example.Stephen miller twitter. The
label
value is what you will see in the tasks list. Name this whatever you like.The
problemMatcher
value selects the output parser to use for finding errors and warnings in the compiler output. For clang++, you'll get the best results if you use the $gcc
problem matcher.The
'isDefault': true
value in the group
object specifies that this task will be run when you press ⇧⌘B (Windows, Linux Ctrl+Shift+B). This property is for convenience only; if you set it to false
, you can still build from the Terminal menu with Terminal > Run Build Task.Note: You can learn more about
tasks.json
variables in the variables reference.Running the build
- Go back to
helloworld.cpp
. Because we want to buildhelloworld.cpp
it is important that this file be the one that is active in the editor for the next step. - To run the build task that you defined in tasks.json, press ⇧⌘B (Windows, Linux Ctrl+Shift+B) or from the Terminal main menu choose Run Build Task.
- When the task starts, you should see the Integrated Terminal window appear below the code editor. After the task completes, the terminal shows output from the compiler that indicates whether the build succeeded or failed. For a successful Clang build, the output looks something like this:
- Create a new terminal using the + button and you'll have a new terminal with the
helloworld
folder as the working directory. Runls
and you should now see the executablehelloworld
along with the debugging file (helloworld.dSYM
). - You can run
helloworld
in the terminal by typing./helloworld
.
Modifying tasks.json
You can modify your
tasks.json
to build multiple C++ files by using an argument like '${workspaceFolder}/*.cpp'
instead of ${file}
. This will build all .cpp
files in your current folder. You can also modify the output filename by replacing '${fileDirname}/${fileBasenameNoExtension}'
with a hard-coded filename (for example '${workspaceFolder}/myProgram.out'
).Posts Tagged by agile manifesto. The Agile Manifesto was written in February of 2001 by seventeen independent-minded software practitioners. While the participants didn't agree about much, they found consensus around four main. We are uncovering better ways of developing softwareby doing it and helping others do it. These are ourvalues and principles. Lecture on principles which were behind the development of Agile Manifesto. Agile manifesto. The Agile Manifesto and especially the 12 underlying principles are fundamental in order to achieve adaptability, flexibility and self-organization as.
Debug helloworld.cpp
Next, you'll create a
launch.json
file to configure VS Code to launch the LLDB debugger when you press F5 to debug the program.From the main menu, choose Run > Add Configuration.. and then choose C++ (GDB/LLDB).
You'll then see a dropdown for predefined debugging configurations. Choose clang++ build and debug active file.
VS Code creates a
launch.json
file, opens it in the editor, and builds and runs 'helloworld'. Your launch.json
file will look something like this:The
program
setting specifies the program you want to debug. Here it is set to the active file folder ${fileDirname}
and active filename ${fileBasenameNoExtension}
, which if helloworld.cpp
is the active file will be helloworld
.By default, the C++ extension won't add any breakpoints to your source code and the
stopAtEntry
value is set to false
.Change the
stopAtEntry
value to true
to cause the debugger to stop on the main
method when you start debugging.Ensure that the
preLaunchTask
value matches the label
of the build task in the tasks.json
file.Start a debugging session
- Go back to
helloworld.cpp
so that it is the active file in the editor. This is important because VS Code uses the active file to determine what you want to debug. - Press F5 or from the main menu choose Run > Start Debugging. Before you start stepping through the source code, let's take a moment to notice several changes in the user interface:
- The Integrated Terminal appears at the bottom of the source code editor. In the Debug Output tab, you see output that indicates the debugger is up and running.
- The editor highlights the first statement in the
main
method. This is a breakpoint that the C++ extension automatically sets for you: - The Run view on the left shows debugging information. You'll see an example later in the tutorial.
- At the top of the code editor, a debugging control panel appears. You can move this around the screen by grabbing the dots on the left side.
Step through the code
Now you're ready to start stepping through the code.
- Click or press the Step over icon in the debugging control panel so that the
for (const string& word : msg)
statement is highlighted.The Step Over command skips over all the internal function calls within thevector
andstring
classes that are invoked when themsg
variable is created and initialized. Notice the change in the Variables window. The contents ofmsg
are visible because that statement has completed. - Press Step over again to advance to the next statement (skipping over all the internal code that is executed to initialize the loop). Now, the Variables window shows information about the loop variable.
- Press Step over again to execute the
cout
statement. Note As of the March 2019 version of the extension, no output will appear in the DEBUG CONSOLE until the lastcout
completes.
Set a watch
You might want to keep track of the value of a variable as your program executes. You can do this by setting a watch on the variable.
- Place the insertion point inside the loop. In the Watch window, click the plus sign and in the text box, type
word
, which is the name of the loop variable. Now view the Watch window as you step through the loop. - To quickly view the value of any variable while execution is paused, you can hover over it with the mouse pointer.
C/C++ configuration
For more control over the C/C++ extension, create a
c_cpp_properties.json
file, which allows you to change settings such as the path to the compiler, include paths, which C++ standard to compile against (such as C++17), and more.Download Visual Studio Code Para Mac
View the C/C++ configuration UI by running the command C/C++: Edit Configurations (UI) from the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)).
This opens the C/C++ Configurations page.
Visual Studio Code places these settings in
.vscode/c_cpp_properties.json
. If you open that file directly, it should look something like this:You only need to modify the Include path setting if your program includes header files that are not in your workspace or the standard library path.
Compiler path
compilerPath
is an important configuration setting. The extension uses it to infer the path to the C++ standard library header files. When the extension knows where to find those files, it can provide useful features like smart completions and Go to Definition navigation.The C/C++ extension attempts to populate
compilerPath
with the default compiler location based on what it finds on your system. The compilerPath
search order is:- Your PATH for the names of known compilers. The order the compilers appear in the list depends on your PATH.
- Then hard-coded XCode paths are searched, such as
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/
Mac framework path
On the C/C++ Configuration screen, scroll down and expand Advanced Settings and ensure that Mac framework path points to the system header files. For example:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks
Reusing your C++ configuration
VS Code is now configured to use Clang on macOS. The configuration applies to the current workspace. To reuse the configuration, just copy the JSON files to a
.vscode
folder in a new project folder (workspace) and change the names of the source file(s) and executable as needed.Troubleshooting
Compiler and linking errors
The most common cause of errors (such as
undefined _main
, or attempting to link with file built for unknown-unsupported file format
, and so on) occurs when helloworld.cpp
is not the active file when you start a build or start debugging. This is because the compiler is trying to compile something that isn't source code, like your launch.json
, tasks.json
, or c_cpp_properties.json
file.If you see build errors mentioning 'C++11 extensions', you may not have updated your
tasks.json
build task to use the clang++ argument --std=c++17
. By default, clang++ uses the C++98 standard, which doesn't support the initialization used in helloworld.cpp
. Make sure to replace the entire contents of your tasks.json
file with the code block provided in the Build helloworld.cpp section.Terminal won't launch For input
On macOS Catalina and onwards, you might have a issue where you are unable to enter input, even after setting
'externalConsole': true
. A terminal window opens, but it does not actually allow you type any input.The issue is currently tracked #5079.
The workaround is to have VS Code launch the terminal once. You can do this by adding and running this task in your
tasks.json
:You can run this specific task using Terminal > Run Task.. and select Open Terminal.
Once you accept the permission request, then the external console should appear when you debug.
Next steps
Visual Studio Code For Beginners
- Explore the VS Code User Guide.
- Review the Overview of the C++ extension
- Create a new workspace, copy your .json files to it, adjust the necessary settings for the new workspace path, program name, and so on, and start coding!