From 9b806299226b5c9c457c8a63685311146152ea0d Mon Sep 17 00:00:00 2001 From: Rageking8 Date: Sun, 31 Aug 2025 21:22:44 +0800 Subject: [PATCH 1/2] Fix miscellaneous spacing issues --- docs/build/reference/fpcvt.md | 2 +- docs/build/reference/ln-create-msil-module.md | 6 +++--- docs/build/reference/midl-property-pages.md | 2 +- ...pgd-specify-database-for-profile-guided-optimizations.md | 2 +- .../tool-errors/linker-tools-error-lnk2022.md | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/build/reference/fpcvt.md b/docs/build/reference/fpcvt.md index 8661d649c92..5e644c5c7da 100644 --- a/docs/build/reference/fpcvt.md +++ b/docs/build/reference/fpcvt.md @@ -40,7 +40,7 @@ The **`/fpcvt`** options are new in Visual Studio 2019 version 16.8. If you spec ### Intrinsic functions for conversions -You can specify the behavior of a specific conversion independently of the **`/fpcvt `** option, which applies globally. The compiler provides intrinsic sentinel conversion functions for conversions compatible with **`/fpcvt:IA`**. For more information, see [Sentinel conversion functions](../../intrinsics/sentinel-conversion-functions.md). The compiler also provides saturation conversion functions compatible with conversions on ARM or ARM64 target architectures. For more information, see [Saturation conversion functions](../../intrinsics/saturation-conversion-functions.md). +You can specify the behavior of a specific conversion independently of the **`/fpcvt`** option, which applies globally. The compiler provides intrinsic sentinel conversion functions for conversions compatible with **`/fpcvt:IA`**. For more information, see [Sentinel conversion functions](../../intrinsics/sentinel-conversion-functions.md). The compiler also provides saturation conversion functions compatible with conversions on ARM or ARM64 target architectures. For more information, see [Saturation conversion functions](../../intrinsics/saturation-conversion-functions.md). The compiler also supports intrinsic conversion functions that execute as quickly as possible for valid conversions. These functions may generate any value or throw an exception for an invalid conversion. The results depend on the target platform, compiler options, and context. They're useful for handling values that have already been range-checked, or values generated in a way that can't cause an invalid conversion. For more information, see [Fast conversion functions](../../intrinsics/fast-conversion-functions.md). diff --git a/docs/build/reference/ln-create-msil-module.md b/docs/build/reference/ln-create-msil-module.md index b5cd351176f..b8a545e5546 100644 --- a/docs/build/reference/ln-create-msil-module.md +++ b/docs/build/reference/ln-create-msil-module.md @@ -21,15 +21,15 @@ By default, `/LN` isn't in effect, and the compiler inserts an assembly manifest When you use `/LN`, you must also use one of the [/clr (Common Language Runtime Compilation)](clr-common-language-runtime-compilation.md) options. -A managed program that doesn't have assembly metadata in the manifest is called a module. If you compile with [/c (Compile Without Linking)](c-compile-without-linking.md) and `/LN`, specify [`/NOASSEMBLY `(Create a MSIL Module)](noassembly-create-a-msil-module.md) in the linker phase to create the output file. +A managed program that doesn't have assembly metadata in the manifest is called a module. If you compile with [/c (Compile Without Linking)](c-compile-without-linking.md) and `/LN`, specify [`/NOASSEMBLY` (Create a MSIL Module)](noassembly-create-a-msil-module.md) in the linker phase to create the output file. -Create modules if you want to take a component-based approach to building assemblies. You can author types and compile them into modules. Then, you can generate an assembly from one or more modules. For more information on creating assemblies from modules, see [`.netmodule` Files as Linker Input](netmodule-files-as-linker-input.md) or [`Al.exe `(Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker). +Create modules if you want to take a component-based approach to building assemblies. You can author types and compile them into modules. Then, you can generate an assembly from one or more modules. For more information on creating assemblies from modules, see [`.netmodule` Files as Linker Input](netmodule-files-as-linker-input.md) or [`Al.exe` (Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker). The default file extension for a module is `.netmodule`. In releases before Visual Studio 2005, you created a module with `/clr:noAssembly`. -The MSVC linker accepts `.netmodule` files as input. The output file produced by the linker is an assembly or `.netmodule` with no run-time dependence on any of the `.netmodule`s that you input to the linker. For more information, see [`.netmodule `Files as Linker Input](netmodule-files-as-linker-input.md). +The MSVC linker accepts `.netmodule` files as input. The output file produced by the linker is an assembly or `.netmodule` with no run-time dependence on any of the `.netmodule`s that you input to the linker. For more information, see [`.netmodule` Files as Linker Input](netmodule-files-as-linker-input.md). ### To set this compiler option in the Visual Studio development environment diff --git a/docs/build/reference/midl-property-pages.md b/docs/build/reference/midl-property-pages.md index 66c3955c39a..5c7d64e42e7 100644 --- a/docs/build/reference/midl-property-pages.md +++ b/docs/build/reference/midl-property-pages.md @@ -123,7 +123,7 @@ Specifies which environment to target ([/env](/windows/win32/midl/-env) arm32|wi ### Generate Stubless Proxies -Generate fully interpreted stubs with extensions and stubless proxies for object interfaces ([/Oicf](/windows/win32/midl/-oi), [/Oif](/windows/win32/midl/-oi) ). +Generate fully interpreted stubs with extensions and stubless proxies for object interfaces ([/Oicf](/windows/win32/midl/-oi), [/Oif](/windows/win32/midl/-oi)). ### Suppress Compiler Warnings diff --git a/docs/build/reference/pgd-specify-database-for-profile-guided-optimizations.md b/docs/build/reference/pgd-specify-database-for-profile-guided-optimizations.md index 77539e99b0c..d8461ded773 100644 --- a/docs/build/reference/pgd-specify-database-for-profile-guided-optimizations.md +++ b/docs/build/reference/pgd-specify-database-for-profile-guided-optimizations.md @@ -7,7 +7,7 @@ helpviewer_keywords: ["-PGD linker option", "/PGD linker option"] --- # /PGD (Specify Database for Profile-Guided Optimizations) -**The /PGD option is deprecated.** Starting in Visual Studio 2015, prefer the [`/GENPROFILE`or `/FASTGENPROFILE`](genprofile-fastgenprofile-generate-profiling-instrumented-build.md) linker options instead. This option is used to specify the name of the .pgd file used by the profile-guided optimization process. +**The /PGD option is deprecated.** Starting in Visual Studio 2015, prefer the [`/GENPROFILE` or `/FASTGENPROFILE`](genprofile-fastgenprofile-generate-profiling-instrumented-build.md) linker options instead. This option is used to specify the name of the .pgd file used by the profile-guided optimization process. ## Syntax diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk2022.md b/docs/error-messages/tool-errors/linker-tools-error-lnk2022.md index eee9aa2821e..477002d9070 100644 --- a/docs/error-messages/tool-errors/linker-tools-error-lnk2022.md +++ b/docs/error-messages/tool-errors/linker-tools-error-lnk2022.md @@ -16,7 +16,7 @@ One way to diagnose this problem is to run **ildasm -tokens** on the object file One reason for LNK2022 is when a type (such as a struct) exists in multiple compilands with the same name, but with conflicting definitions, and when you compile with [/clr](../../build/reference/clr-common-language-runtime-compilation.md). In this case, make sure that the type has an identical definition in all compilands. The type name is listed in `error_message`. -Another possible cause for LNK2022 is when the linker finds a metadata file in a different location than was specified to the compiler (with [#using](../../preprocessor/hash-using-directive-cpp.md) ). Make sure that the metadata file (.dll or .netmodule) is in the same location when passed to the linker, as it was when it was passed to the compiler. +Another possible cause for LNK2022 is when the linker finds a metadata file in a different location than was specified to the compiler (with [#using](../../preprocessor/hash-using-directive-cpp.md)). Make sure that the metadata file (.dll or .netmodule) is in the same location when passed to the linker, as it was when it was passed to the compiler. When building an ATL application, the use of the macro `_ATL_MIXED` is required in all compilands, if it is used in at least one. From 036f251ffd0e583f2b2473374eca99ca9660e47d Mon Sep 17 00:00:00 2001 From: Rageking8 Date: Sun, 31 Aug 2025 21:24:00 +0800 Subject: [PATCH 2/2] Update metadata in 5 topics --- docs/build/reference/fpcvt.md | 2 +- docs/build/reference/ln-create-msil-module.md | 4 ++-- docs/build/reference/midl-property-pages.md | 5 ++--- .../pgd-specify-database-for-profile-guided-optimizations.md | 2 +- .../error-messages/tool-errors/linker-tools-error-lnk2022.md | 5 ++--- 5 files changed, 8 insertions(+), 10 deletions(-) diff --git a/docs/build/reference/fpcvt.md b/docs/build/reference/fpcvt.md index 5e644c5c7da..85446ad72e1 100644 --- a/docs/build/reference/fpcvt.md +++ b/docs/build/reference/fpcvt.md @@ -1,6 +1,6 @@ --- -description: "Learn more about: /fpcvt (Floating-point to integer conversion compatibility)" title: "/fpcvt (Floating-point to unsigned integer conversion compatibility)" +description: "Learn more about: /fpcvt (Floating-point to integer conversion compatibility)" ms.date: 11/03/2021 f1_keywords: ["/fpcvt", "-fpcvt"] helpviewer_keywords: ["-fpcvt compiler option [C++]", "/fpcvt compiler option [C++]"] diff --git a/docs/build/reference/ln-create-msil-module.md b/docs/build/reference/ln-create-msil-module.md index b8a545e5546..4ec40b38bd7 100644 --- a/docs/build/reference/ln-create-msil-module.md +++ b/docs/build/reference/ln-create-msil-module.md @@ -1,7 +1,7 @@ --- -description: "Learn more about: /LN (Create MSIL Module)" title: "/LN (Create MSIL Module)" -ms.date: "11/04/2016" +description: "Learn more about: /LN (Create MSIL Module)" +ms.date: 11/04/2016 f1_keywords: ["/LN"] helpviewer_keywords: ["-LN compiler option [C++]", "/LN compiler option [C++]"] --- diff --git a/docs/build/reference/midl-property-pages.md b/docs/build/reference/midl-property-pages.md index 5c7d64e42e7..73d39a260e2 100644 --- a/docs/build/reference/midl-property-pages.md +++ b/docs/build/reference/midl-property-pages.md @@ -1,9 +1,8 @@ --- -description: "Learn more about: MIDL Property Pages" title: "MIDL Compiler Property Pages" -ms.date: "07/24/2019" +description: "Learn more about: MIDL Property Pages" +ms.date: 07/24/2019 ms.topic: "article" -ms.assetid: 57498a01-fccc-4a0e-a036-6ff702f83126 f1_keywords: - VC.Project.VCMidlTool.PreprocessorDefinitions - VC.Project.VCMidlTool.AdditionalIncludeDirectories diff --git a/docs/build/reference/pgd-specify-database-for-profile-guided-optimizations.md b/docs/build/reference/pgd-specify-database-for-profile-guided-optimizations.md index d8461ded773..746755ec18f 100644 --- a/docs/build/reference/pgd-specify-database-for-profile-guided-optimizations.md +++ b/docs/build/reference/pgd-specify-database-for-profile-guided-optimizations.md @@ -1,6 +1,6 @@ --- -description: "Learn more about: /PGD (Specify Database for Profile-Guided Optimizations)" title: "/PGD (Specify Database for Profile-Guided Optimizations)" +description: "Learn more about: /PGD (Specify Database for Profile-Guided Optimizations)" ms.date: 03/24/2025 f1_keywords: ["VC.Project.VCLinkerTool.ProfileGuidedDatabase"] helpviewer_keywords: ["-PGD linker option", "/PGD linker option"] diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk2022.md b/docs/error-messages/tool-errors/linker-tools-error-lnk2022.md index 477002d9070..56c9f16627b 100644 --- a/docs/error-messages/tool-errors/linker-tools-error-lnk2022.md +++ b/docs/error-messages/tool-errors/linker-tools-error-lnk2022.md @@ -1,10 +1,9 @@ --- -description: "Learn more about: Linker Tools Error LNK2022" title: "Linker Tools Error LNK2022" -ms.date: "11/04/2016" +description: "Learn more about: Linker Tools Error LNK2022" +ms.date: 11/04/2016 f1_keywords: ["LNK2022"] helpviewer_keywords: ["LNK2022"] -ms.assetid: d2128c73-dde3-4b8e-a9b2-0a153acefb3b --- # Linker Tools Error LNK2022