IDE and Tools for Visual C++ Development
In addition to shared tools in the Visual Studio IDE, MSVC has several tools specifically for native code development. These tools are also listed in this article. For a list of which tools are available in each edition of Visual Studio, see Visual C++ Tools and Features in Visual Studio Editions.
Creating a solution and project(s)
A project is basically a set of source code files and resources such as images or data files that are built into an executable file. Visual Studio 2017 can support any build system or custom build tools that you wish to use, with full support for Intellisense, browsing and debugging:
- MSBuild is the native build system for Visual Studio and is often the best choice for Universal Windows Platform (UWP) apps or legacy Windows desktop applications that use MFC or ATL. For more information about MSBuild-based C++ projects, see Creating and managing MSBuild-based projects.
- CMake is a cross-platform build system that is integrated into the Visual Studio IDE when you install the Desktop development with C++ workload. For more information, see CMake projects in Visual C++.
- Any other C++ build system, including a loose collection of files, is supported via the Open Folder feature. You create simple JSON files to invoke your build program and configure debugging sessions. For more information, see Bring your C++ code to Visual Studio.
Project templates (MSBuild)
Visual Studio comes with several templates for MSBuild-based projects; these templates contain starter code and the settings needed for a variety of basic program types. Typically you start by choosing File > New Project to create a project from a project template, then add new source code files to that project, or start coding in the files provided. For information specific to C++ projects and project wizards, see Creating and Managing Visual C++ Projects.
Application wizards (MSBuild)
Visual Studio provides wizards for some MSBuild project types when you choose File > New Project. A wizard guides you step-by-step through the process of creating a new project. This is useful for project types that have many options and settings. For more information, see Creating Desktop Projects By Using Application Wizards.
Creating user interfaces with designers (MSBuild)
If your program has a user interface, one of the first tasks is to populate it with controls such as buttons, list boxes and so on. Visual Studio includes a visual design surface and a toolbox for each flavor of C++ application. No matter which type of app you are creating, the basic idea is the same: you drag a control from the toolbox window and drop it onto the design surface at the desired location. In the background, Visual Studio generates the resources and code required to make it all work. Then you write the code to populate the controls with data or customize their appearance and behavior.
For more information about designing a user interface for a Universal Windows Platform app, see Design and UI.
Writing and editing code
After you create a project, all the project files are displayed in the Solution Explorer window. When you click on a .h or .cpp file in Solution Explorer, the file opens up in the code editor. The code editor is a specialized word processor for C++ source code. It color-codes language keywords, method and variable names, and other elements of your code to make the code more readable and easier to understand.
The code editor also supports several features that together are known as Intellisense. You can hover over a method and see some basic documentation for it. After you type a class variable name and a . or ->, a list of instance members of that class appears. If you type a class name and then a ::, a list of static members appears. When you start typing a class or method name, the code editor will offer suggestions to complete the statement. For more information, see Using IntelliSense.
You can use Intellisense code snippets to generate commonly-used or complicated code constructs with a shortcut keystroke. For more information, see Code Snippets.
The View menu provides access to many windows and tools for navigating around in your code files. For detailed information about these windows, see Viewing the Structure of Code.
In all editions of Visual Studio, use the Solution Explorer pane to navigate between the files in a project. Expand a .h or .cpp file icon to view the classes in the file. Expand a class to see its members. Double-click on a member to navigate to its definition or implementation in the file.
Class View and Code Definition Window
Use the Class View pane to see the namespaces and classes across all the files, including partial classes. You can expand each namespace or class to see its members and double-click on the member to navigate to that location in the source file. If you open the Code Definition Window, you can view the definition or implementation of the type when you choose it in Class View.
Use Object Browser to explore type information in Windows Runtime components (.winmd files), .NET assemblies and COM type libraries. It is not used with Win32 DLLs.
Go To Definition/Declaration
Press F12 on any API name or member variable to go to its definition. If the definition is in a .winmd file (for a UWP or Windows 8.x Store app) then you will be shown the type info in the Object Browser. You can also choose Go To Definition or Go To Declaration by right-clicking on the variable or type name and choosing the option from the context menu.
Find All References
In a source code file, right-click with the mouse cursor over the name of a type or method or variable, and choose Find all References to return a list of every location in the file, project or solution where the type is used. Find All References is intelligent and only returns instances of the same identical variable, even if other variables at different scope have the same name.
Add and edit resources (MSBuild)
The term resource in the context of a Visual Studio desktop project includes things such as dialog boxes, icons, localizable strings, splash screens, database connection strings, or any arbitrary data that you want to include in the executable file.
For more information on adding and editing resources in native desktop C++ projects, see Working with Resource Files.
Build (compile and link)
Choose Build > Build Solution on the menu bar, or enter the Ctrl+Shift+B key combination to compile and link a project. To create executable code, Visual Studio uses MSBuild or CMake or whatever build environment you set up via Open Folder. For MSBuild projects, you set general build options under Tools > Options > Projects and Solutions and you can set properties for specific projects under Project > Properties. Build errors and warnings are reported in the Error List (Ctrl+\, E). Non-MSBuild projects are configured with JSON files that you create in Solution Explorer. Whatever build system you use, the Output Window (Alt+2) shows information about the build process. For more information about MSBuild configurations, see Working with Project Properties and Building C++ Projects in Visual Studio.
You can also use the compiler (cl.exe) and many other build-related standalone tools such as NMAKE and LIB directly from the command line. For more information, see Build C/C++ code on the command line and C/C++ Building Reference.
Visual Studio includes a unit test framework for both native C++ and C++/CLI. For more information, see Verifying Code by Using Unit Tests and Writing Unit tests for C/C++ with the Microsoft Unit Testing Framework for C++
You can debug your program by pressing F5 when your project configuration is set to Debug. While debugging you can set breakpoints by pressing F9, step through code by pressing F10, view the values of specified variables or registers, and even in some cases make changes in code and continue debugging without re-compiling. For more information, see Debugging in Visual Studio.
Deploy completed applications
You deploy a UWP app to customers through the Microsoft Store through the Project > Store menu option. Deployment of the CRT is handled automatically behind the scenes. For more information, see Selling Apps.
When you deploy a native C++ desktop application to another computer, you must install the application itself and any library files that the application depends on. There are three ways to deploy the Universal C++ runtime (UCRT) with an application: central deployment, local deployment, or static linking. For more information, see Deploying Desktop Applications.
For more information about deploying a C++/CLI program, see Deployment Guide for Developers,
|Visual C++ Tools and Features in Visual Studio Editions||Shows which features are available in the various editions of Visual Studio.|
|Creating and managing MSBuild-based projects||Provides an overview of C++ MSBuild-based projects in Visual Studio and links to other articles that explain how to create and manage them.|
|CMake projects in Visual C++.||Describes how to build CMake or other non-MSBuild projects in Visual C++.|
|Building C/C++ Programs||Describes how to build C++ projects.|
|Deploying Desktop Applications||Provides an overview of deployment for C++ apps and links to other articles that describe deployment in detail.|
|Visual C++ Porting and Upgrading Guide||Detailed information about how to upgrade C++ applications that were created in earlier versions of Visual Studio, and also how to migrate applications that were created by using tools other than Visual Studio.|
|Visual C++||Describes key features of Visual C++ in Visual Studio and links to the rest of the Visual C++ documentation.|