Download Visual Studio Community, Professional, and Enterprise. Try Visual Studio IDE, Code or Mac for free today. Visual Studio 2008 reached end of support on April 10, 2018. To aid the discovery of the latest downloads, the links are retained currently, but may be removed in the future. Download the Visual Studio 2008 Service Pack 1 (Installer). This is the latest Visual C service pack for Visual Studio 2008.
- Visual Studio for Mac (C Support) cppcompiler. Mehmet Ozuag reported Mar 20 at 12:30 PM. Show comments 2. 10 40000 characters needed characters left characters exceeded. Viewable by All Microsoft Only. Feedback Bot Mar 23 at 10:40 AM.
- MonoDevelop (also known as Xamarin Studio) is an open-source integrated development environment for Linux, macOS, and Windows. Its primary focus is development of projects that use Mono and.NET Framework.MonoDevelop integrates features similar to those of NetBeans and Microsoft Visual Studio, such as automatic code completion, source control, a graphical user interface (GUI) and Web designer.
A new version of Microsoft's integrated development environment (IDE) goes live today with the release of Visual Studio 2019 and its cousin Visual Studio 2019 for Mac.
Visual Studio is in a bit of a strange position, and it would be fair for developers to ask why this branded release even exists. Visual Studio 2017 has received nine point releases and countless patch releases since its release two years ago. Each of these releases has brought a mix of new features and bug fixes, and for Visual Studio users, the experience feels comparable to that of, say, Google Chrome, where each new version brings a steady flow of incrementally improved features and fixes.
Indeed, this iterative, incremental model is the one that Microsoft is pushing (and using) for services such as Azure DevOps and is comparable to the continuous development we see for Office 365, which is updated monthly, and the free and open source Visual Studio Code, which also has monthly iterations. With this development process in place, one wonders why we'd bother with 'Visual Studio 2019' at all; let's just have 'Visual Studio' and keep on updating it forever.
The reasons for sticking to the old way of releasing? There are customers who buy perpetual licenses, and a new major version provides an easy opportunity to make certain breaking changes, such as dropping support for old platforms or making certain major changes to the C++ library. To that end, Visual Studio 2019 (finally) drops Windows XP support for C++ projects; you'll have to use the old Visual Studio 2017 C++ compiler if you want to continue targeting the long-obsolete operating system. A new major version is also a good time to make larger user interface changes, and indeed, some of the first things that will be noticed on installing Visual Studio 2019 are the new welcome screen, a new interface for creating projects, and a new title bar that incorporates both the application's menu and a revamped search feature for finding features within the IDE.
Accordingly, the new version does bring a number of bits and pieces that haven't been added to 2017. The one I'm most excited for is the general availability of Live Share. Live Share is a collaborative editing system that works in both Visual Studio and Visual Studio Code, allowing pairs of developers to code and debug together while still seeing their own preferred editor setup. The initial preview of Live Share, back in November 2017, only supported JavaScript (and Microsoft's highly successful TypeScript variant) and C#.
In response to user demand, C++ and Python have been added to the Live Share experience. Python is still something of a novelty in Visual Studio; support for the scripting language was added to Visual Studio 2017 in one of its point releases. Visual Studio 2019 expands on this with support for multiple Python runtime environments, making it easier to switch between interpreters and versions, a more capable debugger, and smarter IntelliSense completion.
C++ developers will benefit from a compiler with a better optimizer, better support for projects built using CMake, and partial support for enforcing the C++ lifetime profile, a set of static, compile-time rules that enable the compiler to detect and warn about unsafe use of pointers and iterators.
With GitHub now a part of Microsoft, Visual Studio is picking up more GitHub integration; 2019 adds the support for GitHub's Pull Request model for managing the integration of patches into a codebase directly within the IDE. The IDE now also includes support for Git's 'stash' feature that allows a set of changes to be temporarily stored so you can switch to a different branch without having to commit them or risk losing them.
As with any new Visual Studio release, there's also the usual range of updated compilers and language versions, such as a preview of C# 8.0 features, new refactorings, and so on.
AdvertisementVisual Studio for Mac, derived from the Xamarin IDE that Microsoft acquired when it bought the cross-platform .NET company, is also updated today. The first iteration of Visual Studio for Mac was basically a rebrand of the Xamarin Studio app—updated to include Microsoft's C# compiler and .NET libraries, instead of Xamarin's clones—with little real relationship to 'real' Visual Studio.
However, Microsoft does appear to be making a real effort to bring the products together in those areas that make sense. Visual Studio 2019 for Mac includes a preview of a new text editor that's built on the same engine as the one in Visual Studio for Windows, with a native macOS user interface and capabilities. This means that both Visual Studios have very similar capabilities in things like IntelliSense, code completion, and quick fixes. The new editor isn't on by default, but it can be enabled for C# and XAML, with more languages planned once those are stabilized. The welcome screen also looks much like its new Windows counterpart.
Microsoft is unifying the experiences in other areas, too; the Unity debugger is now the same between Mac and Windows, and Microsoft intends to bring portions of the Windows Xamarin Forms XAML experience to Mac in a future update.
On top of this, there are numerous performance and stability improvements and lots of accessibility improvements to help those using assistive technologies.
With both Visual Studio for Windows and for Mac, Microsoft has emphasized the importance of user feedback in the development process. Both the point releases and the major updates are guided by user feedback, with, for example, the new Python and Live Share features coming in direct response to user requests. The regular flow of point releases enables Microsoft to put functionality in front of users much sooner than it could with only major updates, and that functionality can be re-shaped and extended in response to feedback. Compared to the olden days of Visual Studio, when you'd file bugs on the Connect site only to have them disappear forever, the experience today is a welcome and refreshing improvement.
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. Convert mp4 to mp3 on mac os x.
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 Is ipad mini 5 good for pubg. 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.cppuses C++17 language features.- Changes the current working directory directive (
'cwd') to the folder wherehelloworld.cppis.
C++ Visual Studio Mac
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.
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 task.json variables in the variables reference.
C++ Visual Studio For Mac
Running the build
Go back to
helloworld.cpp. Because we want to buildhelloworld.cppit is important that this file be the one that is active in the editor for the next step. How to start mac from bootable usb.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
helloworldfolder as the working directory. Runlsand you should now see the executablehelloworldalong with the debugging file (helloworld.dSYM).You can run
helloworldin 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').
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 task.json file.
Start a debugging session
- Go back to
helloworld.cppso 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
mainmethod. 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 the
vectorandstringclasses that are invoked when themsgvariable is created and initialized. Notice the change in the Variables window. The contents ofmsgare visible because that statement has completed.Ssd drive apple macbook pro. 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
coutstatement. Note As of the March 2019 version of the extension, no output will appear in the DEBUG CONSOLE until the lastcoutcompletes.
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.
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)).
Burn mp4 to dvd mac. 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:
Visual Studio Code Free
- 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 task.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 task.json file with the code block provided in the Build helloworld.cpp section.
Next steps
- 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!
