Skip to content

Commit fa6f614

Browse files
author
mikeblome
committed
fixed images and heading in open folder topic
1 parent 2ad47d2 commit fa6f614

File tree

5 files changed

+8
-21
lines changed

5 files changed

+8
-21
lines changed

‎docs/ide/TOC.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@
1313
## [Tasks.vs.json schema reference (C++)](tasks-vs-json-schema-reference-cpp.md)
1414
# [CMake projects](cmake-tools-for-visual-cpp.md)
1515
## [Tutorial: Create C++ cross-platform projects in Visual Studio](get-started-linux-cmake.md)
16+
## [Configure a Linux CMake project](../linux/cmake-linux-project.md)
1617
## [Customize CMake settings](customize-cmake-settings.md)
1718
## [Configure CMake debugging sessions](configure-cmake-debugging-sessions.md)
1819
## [CMake predefined configuration schema reference](cmake-predefined-configuration-reference.md)

‎docs/ide/get-started-linux-cmake.md‎

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -175,16 +175,8 @@ So now you have seen the same code base, cloned directly from GitHub, build, run
175175

176176
## Next steps
177177

178-
Learn more about the CMakeSettings and launch.vs.json file schemas:
178+
Learn more about configuring and debugging CMake projects in Visual Studio:
179179
> [!div class="nextstepaction"]
180180
> [Configure CMake debugging sessions](configure-cmake-debugging-sessions.md)
181181
> [CMake predefined configuration reference](cmake-predefined-configuration-reference.md)
182182
183-
<!--- Required:
184-
Tutorials should always have a Next steps H2 that points to the next
185-
logical tutorial in a series, or, if there are no other tutorials, to
186-
some other cool thing the customer can do. A single link in the blue box
187-
format should direct the customer to the next article - and you can
188-
shorten the title in the boxes if the original one doesn't fit.
189-
Do not use a "More info section" or a "Resources section" or a "See also
190-
section". --->

‎docs/ide/media/cmake-bullet3-linux-configuration-item.png‎

-2.46 KB
Loading

‎docs/ide/media/cmake-bullet3-manage-configurations.png‎

-6.44 KB
Loading

‎docs/ide/non-msbuild-projects.md‎

Lines changed: 6 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,18 @@
11
---
2-
title: "Open Folder projects in Visual C++"
3-
ms.date: "06/01/2018"
2+
title: "Open Folder support for C++ build systems in Visual Studio"
3+
ms.date: "01/21/2019"
44
helpviewer_keywords: ["Open Folder Projects in Visual C++"]
55
ms.assetid: abd1985e-3717-4338-9e80-869db5435175
66
---
7-
# Open Folder projects in Visual C++
7+
# Open Folder projects for C++
88

9-
In Visual Studio 2017 and later, the "Open Folder" feature enables you to open a folder of source files and immediately start coding with support for IntelliSense, browsing, refactoring, debugging, and so on. No .sln or .vcxproj files are loaded; if needed, you can specify custom tasks as well as build and launch parameters through simple .json files.
9+
In Visual Studio 2017 and later, the "Open Folder" feature enables you to open a folder of source files and immediately start coding with support for IntelliSense, browsing, refactoring, debugging, and so on. No .sln or .vcxproj files are loaded; if needed, you can specify custom tasks as well as build and launch parameters through simple .json files. For general information about Open Folder, see [Develop code in Visual Studio without projects or solutions](/visualstudio/ide/develop-code-in-visual-studio-without-projects-or-solutions).
1010

11-
For general information about Open Folder, see [Develop code in Visual Studio without projects or solutions](/visualstudio/ide/develop-code-in-visual-studio-without-projects-or-solutions).
11+
CMake is integrated in the Visual Studio IDE as CMake Tools for Visual C++, a component of the C++ desktop workload. For more information, see [CMake projects in Visual Studio](cmake-tools-for-visual-cpp.md). For any other build system, you can use the Open Folder feature. Open Folder effectively decouples the code editor, debugger and analyzers from the build system and the compiler toolset. You can use the C++ code editor with its rich IntelliSense features, the code analyzers, and the Visual Studio debugger with virtually any build system, including CMake, Ninja, QMake (for Qt projects), gyp, SCons, Gradle, Buck, make and more. It even works with a single file or a loose collection of files with no build system.
1212

13-
The Open Folder feature effectively decouples the code editor, debugger and analyzers from the build system and the compiler toolset. You can use the C++ code editor with its rich IntelliSense features, the code analyzers, and the Visual Studio debugger with virtually any build system, including CMake, Ninja, QMake (for Qt projects), gyp, SCons, Gradle, Buck, make and more. It even works with a single file or a loose collection of files with no build system.
14-
15-
To use Open Folder, from the main menu select *File | Open | Folder* or press *Ctrl + Shift + Alt + O*.
13+
To use Open Folder, from the main menu select **File | Open | Folder** or press **Ctrl + Shift + Alt + O**.
1614
Solution Explorer immediately displays all the files in the folder. You can click on any file to begin editing it. In the background, Visual Studio starts indexing the files to enable IntelliSense, navigation, and refactoring features. As you edit, create, move, or delete files, Visual Studio tracks the changes automatically and continuously updates its IntelliSense index.
1715

18-
## CMake projects
19-
20-
CMake is integrated in the Visual Studio IDE as CMake Tools for Visual C++, a component of the C++ desktop workload. For more information, see [CMake Tools for Visual C++](cmake-tools-for-visual-cpp.md).
21-
2216
## QMake projects that target the Qt framework
2317

2418
You can use CMake Tools for Visual C++ to target Qt to build Qt projects, or you can use the [Qt Visual Studio Extension](https://download.qt.io/development_releases/vsaddin/) for either Visual Studio 2015 or Visual Studio 2017.

0 commit comments

Comments
 (0)