Skip to content

Commit 46f32c9

Browse files
author
mikeblome
committed
more moves
1 parent 53c178f commit 46f32c9

313 files changed

Lines changed: 414 additions & 1197 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/build/adding-references-in-visual-cpp-projects.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ In other types of projects such as UWP projects or C++/CLI projects, or when the
1515

1616
In a native C++ project (ATL) the concept of *references* only applies to other projects in the solution, including shared projects, so that is all you see in **Reference Manager**:
1717

18-
![Visual C++ Reference Manager (ATL Projects)](../ide/media/visual-c---reference-manager--atl-projects-.png "Visual C++ Reference Manager (ATL Projects)")
18+
![Visual C++ Reference Manager (ATL Projects)](media/visual-c---reference-manager--atl-projects-.png "Visual C++ Reference Manager (ATL Projects)")
1919

2020
In a C++/CLI or Universal Windows Platform project, the concept of references applies to more kinds of binaries in addition to other projects in the solution. These are all exposed in **Reference Manager**.
2121

@@ -133,5 +133,5 @@ The following properties are found on COM and .NET assembly references, and cann
133133

134134
## See Also
135135

136-
[Property Pages](../ide/property-pages-visual-cpp.md)<br>
136+
[Property Pages](property-pages-visual-cpp.md)<br>
137137
[Working with Project Properties](working-with-project-properties.md)

‎docs/build/application-settings-makefile-project-wizard.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,5 +30,5 @@ Provide the information for the project. The options you specify are reflected i
3030
[Makefile Project Wizard](makefile-project-wizard.md)<br>
3131
[Creating a Makefile Project](..creating-a-makefile-project.md)<br>
3232
[Visual C++ Project Types](visual-cpp-project-types.md)<br>
33-
[Creating Desktop Projects By Using Application Wizards](../ide/creating-desktop-projects-by-using-application-wizards.md)<br>
34-
[Property Pages](../ide/property-pages-visual-cpp.md)
33+
[Creating Desktop Projects By Using Application Wizards](creating-desktop-projects-by-using-application-wizards.md)<br>
34+
[Property Pages](property-pages-visual-cpp.md)

‎docs/build/build-system-changes.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ When **Solution Explorer** is used to add a file to a project, the filters file
5252

5353
## VC++ Directories Settings
5454

55-
Visual C++ directories settings are specified on the [VC++ Directories Property Page](../ide/vcpp-directories-property-page.md). In earlier releases of Visual Studio, directories settings apply per-user and the list of excluded directories is specified in the sysincl.dat file.
55+
Visual C++ directories settings are specified on the [VC++ Directories Property Page](vcpp-directories-property-page.md). In earlier releases of Visual Studio, directories settings apply per-user and the list of excluded directories is specified in the sysincl.dat file.
5656

5757
You cannot change the VC++ directories settings if you run [devenv /resetsettings](/visualstudio/ide/reference/resetsettings-devenv-exe) at the command line. You also cannot change the settings if you open the **Tools** menu, click **Import and Export Settings**, and then select the **Reset all settings** option.
5858

‎docs/build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Visual C++ supports a deployment model for Windows client applications based on
1010

1111
Building C/C++ programs as isolated applications presents a range of advantages. For example, an isolated application is unaffected when other C/C++ applications install or uninstall Visual C++ libraries. Visual C++ libraries used by isolated applications may still be redistributed in either the application's local folder, or by installation to the native assembly cache (WinSxS); however, servicing of Visual C++ libraries for already deployed applications can be simplified by using a [publisher configuration file](/windows/desktop/SbsCs/publisher-configuration). The isolated application deployment model makes it easier to ensure that C/C++ applications that are running on a specific computer use the most recent version of Visual C++ libraries, while still leaving open the possibility for system administrators and application authors to control explicit version binding of applications to their dependent DLLs.
1212

13-
This section discusses how you can build your C/C++ application as an isolated application and ensure that it binds to Visual C++ libraries using a manifest. The information in this section primarily applies to native, or unmanaged, Visual C++ applications. For information about deploying native applications built with Visual C++, see [Redistributing Visual C++ Files](../ide/redistributing-visual-cpp-files.md).
13+
This section discusses how you can build your C/C++ application as an isolated application and ensure that it binds to Visual C++ libraries using a manifest. The information in this section primarily applies to native, or unmanaged, Visual C++ applications. For information about deploying native applications built with Visual C++, see [Redistributing Visual C++ Files](redistributing-visual-cpp-files.md).
1414

1515
## In This Section
1616

@@ -32,4 +32,4 @@ This section discusses how you can build your C/C++ application as an isolated a
3232

3333
[Isolated Applications and Side-by-side Assemblies](/windows/desktop/SbsCs/isolated-applications-and-side-by-side-assemblies-portal)
3434

35-
[Deploying Desktop Applications](../ide/deploying-native-desktop-applications-visual-cpp.md)
35+
[Deploying Desktop Applications](deploying-native-desktop-applications-visual-cpp.md)

‎docs/build/building-c-cpp-programs.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ You can build Visual C++ projects either in Visual Studio or on the command line
1111

1212
## In This Section
1313

14-
[Building C++ Projects in Visual Studio](../ide/building-cpp-projects-in-visual-studio.md)<br/>
14+
[Building C++ Projects in Visual Studio](building-cpp-projects-in-visual-studio.md)<br/>
1515
Discusses how to use the Visual Studio IDE to build your C/C++ project.
1616

1717
[Build C/C++ code on the command line](../build/building-on-the-command-line.md)<br/>

‎docs/build/building-c-cpp-side-by-side-assemblies.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,6 @@ This change may allow deployment of corresponding DLLs as a [private assembly](/
2424

2525
## See Also
2626

27-
[Deployment Examples](../ide/deployment-examples.md)<br/>
27+
[Deployment Examples](deployment-examples.md)<br/>
2828
[Building C/C++ Isolated Applications](../build/building-c-cpp-isolated-applications.md)<br/>
2929
[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)

‎docs/build/building-cpp-projects-in-visual-studio.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ To build a project that's selected in **Solution Explorer**, you can:
3232

3333
When you build a Visual C++ application in Visual Studio, you can modify many of the build's settings in the project's Property Pages dialog box. For information about how to set project properties, see [Working with Project Properties](working-with-project-properties.md).
3434

35-
For an example about how to use the IDE to create, build, and debug a C++ project, see [Walkthrough: Explore the Visual Studio IDE with C++](/visualstudio/ide/getting-started-with-cpp-in-visual-studio). For an example about how to use the IDE to build a C++/CLR project, see [Walkthrough: Compiling a C++ Program that Targets the CLR in Visual Studio](../ide/walkthrough-compiling-a-cpp-program-that-targets-the-clr-in-visual-studio.md). For an example about how to use the IDE to create a Windows Runtime app, see [Create your first Windows Runtime app using C++](https://msdn.microsoft.com/library/windows/apps/hh974580.aspx).
35+
For an example about how to use the IDE to create, build, and debug a C++ project, see [Walkthrough: Explore the Visual Studio IDE with C++](/visualstudio/ide/getting-started-with-cpp-in-visual-studio). For an example about how to use the IDE to build a C++/CLR project, see [Walkthrough: Compiling a C++ Program that Targets the CLR in Visual Studio](walkthrough-compiling-a-cpp-program-that-targets-the-clr-in-visual-studio.md). For an example about how to use the IDE to create a Windows Runtime app, see [Create your first Windows Runtime app using C++](https://msdn.microsoft.com/library/windows/apps/hh974580.aspx).
3636

3737
To read more about how to build, modify build settings, and specify custom build steps, see the following articles.
3838

@@ -41,13 +41,13 @@ To read more about how to build, modify build settings, and specify custom build
4141
[Understanding Custom Build Steps and Build Events](understanding-custom-build-steps-and-build-events.md)<br>
4242
Describes how to customize the build process in the integrated development environment.
4343

44-
[Common Macros for Build Commands and Properties](../ide/common-macros-for-build-commands-and-properties.md)<br>
44+
[Common Macros for Build Commands and Properties](common-macros-for-build-commands-and-properties.md)<br>
4545
Lists macros that you can use where strings are accepted.
4646

47-
[Building External Projects](../ide/building-external-projects.md)<br>
47+
[Building External Projects](building-external-projects.md)<br>
4848
Discusses building projects that use facilities outside the integrated development environment.
4949

50-
[Project Files](../ide/project-files.md)<br>
50+
[Project Files](project-files.md)<br>
5151
Presents the XML structure of a .vcxproj file.
5252

5353
## Related Sections

‎docs/build/concepts-of-isolated-applications-and-side-by-side-assemblies.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ You can change side-by-side assembly dependencies after an application has been
2424

2525
## Visual C++ libraries
2626

27-
In Visual Studio 2005 and Visual Studio 2008, redistributable libraries such as ATL, MFC, CRT, Standard C++, OpenMP, and MSDIA were deployed as shared side-by-side assemblies to the native assembly cache. In the current version, the redistributable libraries use central deployment. By default, all applications that are built by using Visual C++ are built with the manifest embedded in the final binary, and the manifest describes the dependencies of the binary on the Visual C++ libraries. To understand manifest generation for Visual C++ applications, see [Understanding Manifest Generation for C/C++ Programs](../build/understanding-manifest-generation-for-c-cpp-programs.md). A manifest is not required for applications that are statically linked to the libraries that they use, or that use local deployment. For more information about deployment, see [Deployment in Visual C++](../ide/deployment-in-visual-cpp.md).
27+
In Visual Studio 2005 and Visual Studio 2008, redistributable libraries such as ATL, MFC, CRT, Standard C++, OpenMP, and MSDIA were deployed as shared side-by-side assemblies to the native assembly cache. In the current version, the redistributable libraries use central deployment. By default, all applications that are built by using Visual C++ are built with the manifest embedded in the final binary, and the manifest describes the dependencies of the binary on the Visual C++ libraries. To understand manifest generation for Visual C++ applications, see [Understanding Manifest Generation for C/C++ Programs](../build/understanding-manifest-generation-for-c-cpp-programs.md). A manifest is not required for applications that are statically linked to the libraries that they use, or that use local deployment. For more information about deployment, see [Deployment in Visual C++](deployment-in-visual-cpp.md).
2828

2929
## See Also
3030

‎docs/build/creating-a-makefile-project.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The output file that you specify in the project has no effect on the name that t
2727

2828
1. From the Visual Studio start page, type "makefile" in the **New Project** search box. Or, in the **New Project** dialog box, expand **Visual C++** > **General** (Visual Studio 2015) or **Other** (Visual Studio 2017) and then select **Makefile Project** in the Templates pane to open the project wizard.
2929

30-
1. In the [Application Settings](../ide/application-settings-makefile-project-wizard.md) page, provide the command, output, clean, and rebuild information for debug and retail builds.
30+
1. In the [Application Settings](application-settings-makefile-project-wizard.md) page, provide the command, output, clean, and rebuild information for debug and retail builds.
3131

3232
1. Click **Finish** to close the wizard and open the newly created project in **Solution Explorer**.
3333

‎docs/build/how-to-configure-visual-cpp-projects-to-target-64-bit-platforms.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -36,11 +36,11 @@ You can use the project configurations in the Visual Studio IDE to set up C++ ap
3636

3737
- The [/MACHINE](../build/reference/machine-specify-target-platform.md) linker option is set to **/MACHINE:X64**.
3838

39-
- **Register Output** is turned OFF. For more information, see [Linker Property Pages](../ide/linker-property-pages.md).
39+
- **Register Output** is turned OFF. For more information, see [Linker Property Pages](linker-property-pages.md).
4040

41-
- **Target Environment** is set to **/env x64**. For more information, see [MIDL Property Pages: General](../ide/midl-property-pages-general.md).
41+
- **Target Environment** is set to **/env x64**. For more information, see [MIDL Property Pages: General](midl-property-pages-general.md).
4242

43-
- **Validate Parameters** is cleared and reset to the default value. For more information, see [MIDL Property Pages: Advanced](../ide/midl-property-pages-advanced.md).
43+
- **Validate Parameters** is cleared and reset to the default value. For more information, see [MIDL Property Pages: Advanced](midl-property-pages-advanced.md).
4444

4545
- If **Debug Information Format** was set to **/ZI** in the Win32 project configuration, then it is set to **/Zi** in the 64-bit project configuration. For more information, see [/Z7, /Zi, /ZI (Debug Information Format)](../build/reference/z7-zi-zi-debug-information-format.md).
4646

0 commit comments

Comments
 (0)