@@ -157,5 +157,5 @@ The following properties are found on COM and .NET assembly references, and cann
 
 ## See Also
 
-[Property Pages](property-pages-visual-cpp.md)<br>
+[Property Pages](reference/property-pages-visual-cpp.md)<br>
 [Working with Project Properties](working-with-project-properties.md)
@@ -43,4 +43,4 @@ bounce.exe : up.obj
 
 ## See Also
 
-[Targets](reference/targets.md)
+[Targets](targets.md)
@@ -77,4 +77,4 @@ When you add an item to a project, you add the item to all configurations for th
 ## See Also
 
 [Creating and Managing Visual C++ Projects](../creating-and-managing-visual-cpp-projects.md)<br>
-[Visual C++ Project Types](../visual-cpp-project-types.md)<br>
+[Visual C++ Project Types](visual-cpp-project-types.md)<br>
@@ -19,7 +19,7 @@ Forces parameters passed in registers to be written to their locations on the st
 
 This compiler option is only for the x64 compilers (native and cross compile).
 
-When parameters are passed in an x64 compilation, calling conventions require stackspace for parameters, even for parameters passed in registers. For more information, see [Parameter Passing](parameter-passing.md). However, by default in a release build, the register parameters will not be written to the stack, into the space that is already provided for the parameters. This makes it difficult to debug an optimized (release) build of your program.
+When parameters are passed in an x64 compilation, calling conventions require stackspace for parameters, even for parameters passed in registers. For more information, see [Parameter Passing](../parameter-passing.md). However, by default in a release build, the register parameters will not be written to the stack, into the space that is already provided for the parameters. This makes it difficult to debug an optimized (release) build of your program.
 
 For a release build, use **/homeparams** to ensure that you can debug your application. **/homeparams** does imply a performance disadvantage, because it does require a cycle to load the register parameters on to the stack.
 
 
@@ -10,4 +10,4 @@ An inferred dependent is derived from an inference rule and is evaluated before
 
 ## See Also
 
-[Dependents](reference/dependents.md)
+[Dependents](dependents.md)
@@ -1,6 +1,6 @@
 ---
 title: "Manifest Tool Isolated COM Properties (Visual C++)"
-ms.date: "11/04/2016"
+ms.date: "12/10/2018"
 f1_keywords: ["VC.Project.VCManifestTool.RegistrarScriptFile", "VC.Project.VCManifestTool.ComponentFileName", "VC.Project.VCManifestTool.TypeLibraryFile", "VC.Project.VCManifestTool.ReplacementsFile"]
 ms.assetid: 457582b8-cfde-49c0-92e3-3a6b9e8c08eb
 ---
@@ -12,7 +12,7 @@ To access this property page dialog box, open the property pages for your projec
 
 ## Task List
 
-- [How to: Build Isolated Applications to Consume COM Components](how-to-build-isolated-applications-to-consume-com-components.md)
+- [How to: Build Isolated Applications to Consume COM Components](../how-to-build-isolated-applications-to-consume-com-components.md)
 
 ## UIElement List
 
@@ -36,5 +36,5 @@ To access this property page dialog box, open the property pages for your projec
 
 [Isolated Applications](/windows/desktop/SbsCs/isolated-applications)<br>
 [ClickOnce Application Manifest](/visualstudio/deployment/clickonce-application-manifest)<br>
-[Manifest Tool Property Pages](reference/manifest-tool-property-pages.md)<br>
-[Working with Project Properties](working-with-project-properties.md)
+[Manifest Tool Property Pages](manifest-tool-property-pages.md)<br>
+[Working with Project Properties](../working-with-project-properties.md)
@@ -12,7 +12,7 @@ link.exe now accepts MSIL .obj and .netmodules as input. The output file produce
 
 You must pass to the linker the .obj file from the Visual C++ compilation that created the .netmodule. Passing in a .netmodule is no longer supported because the **/clr:pure** and **/clr:safe** compiler options are deprecated in Visual Studio 2015 and unsupported in Visual Studio 2017.
 
-For information on how to invoke the linker from the command line, see [Linker Command-Line Syntax](linking.md), [Build C/C++ code on the command line](building-on-the-command-line.md), and [Set the Path and Environment Variables for Command-Line Builds](setting-the-path-and-environment-variables-for-command-line-builds.md).
+For information on how to invoke the linker from the command line, see [Linker Command-Line Syntax](linking.md), [Build C/C++ code on the command line](../building-on-the-command-line.md), and [Set the Path and Environment Variables for Command-Line Builds](../setting-the-path-and-environment-variables-for-command-line-builds.md).
 
 Passing a .netmodule or .dll file to the linker that was compiled by the Visual C++ compiler with **/clr** can result in a linker error. For more information, see [Choosing the Format of .netmodule Input Files](choosing-the-format-of-netmodule-input-files.md).
 
 
@@ -20,4 +20,4 @@ NMAKE looks for a dependent first in the current directory, and then in director
 
 ## See Also
 
-[Dependents](reference/dependents.md)
+[Dependents](dependents.md)
@@ -30,7 +30,7 @@ Variables of the following types are tested on a 32-bit operating system as if t
 
 - pointer
 
-If you regularly compile your application by using a compiler that builds 64-bit, x64 code, you can just disable **/Wp64** in your 32-bit compilations because the 64-bit compiler will detect all issues. For more information about how to target a Windows 64-bit operating system, see [Configure Visual C++ for 64-bit, x64 targets](configuring-programs-for-64-bit-visual-cpp.md).
+If you regularly compile your application by using a compiler that builds 64-bit, x64 code, you can just disable **/Wp64** in your 32-bit compilations because the 64-bit compiler will detect all issues. For more information about how to target a Windows 64-bit operating system, see [Configure Visual C++ for 64-bit, x64 targets](../configuring-programs-for-64-bit-visual-cpp.md).
 
 ### To set this compiler option in the Visual Studio development environment
 
 
@@ -9,6 +9,6 @@ ms.assetid: 1629c850-e2db-4678-83d8-9bfc85323bc5
 
 profile database 'pgd_file' is for a different architecture
 
-A .pgd file that was generated from the /LTCG:PGINSTRUMENT operation for another platform was passed to [/LTCG:PGOPTIMIZE](../../build/reference/ltcg-link-time-code-generation.md) . [Profile-guided optimizations](../../build/reference/profile-guided-optimizations.md) are available for x86 and x64 platforms. However, a .pgd file generated with a /LTCG:PGINSTRUMENT operation for one platform is not valid as input to a /LTCG:PGOPTIMIZE for a different platform.
+A .pgd file that was generated from the /LTCG:PGINSTRUMENT operation for another platform was passed to [/LTCG:PGOPTIMIZE](../../build/reference/ltcg-link-time-code-generation.md) . [Profile-guided optimizations](../../build/profile-guided-optimizations.md) are available for x86 and x64 platforms. However, a .pgd file generated with a /LTCG:PGINSTRUMENT operation for one platform is not valid as input to a /LTCG:PGOPTIMIZE for a different platform.
 
 To resolve this error, only pass a .pgd file that is created with /LTCG:PGINSTRUMENT to /LTCG:PGOPTIMIZE on the same platform.
Original file line number	Diff line number	Diff line change
`@@ -43,4 +43,4 @@ bounce.exe : up.obj`
`43`	`43`
`44`	`44`	`## See Also`
`45`	`45`
`46`		`-[Targets](reference/targets.md)`
	`46`	`+[Targets](targets.md)`
Original file line number	Diff line number	Diff line change
`@@ -10,4 +10,4 @@ An inferred dependent is derived from an inference rule and is evaluated before`
`10`	`10`
`11`	`11`	`## See Also`
`12`	`12`
`13`		`-[Dependents](reference/dependents.md)`
	`13`	`+[Dependents](dependents.md)`
Original file line number	Diff line number	Diff line change
`@@ -20,4 +20,4 @@ NMAKE looks for a dependent first in the current directory, and then in director`
`20`	`20`
`21`	`21`	`## See Also`
`22`	`22`
`23`		`-[Dependents](reference/dependents.md)`
	`23`	`+[Dependents](dependents.md)`