Skip to content

Commit 6378472

Browse files
TaojunshenTaojunshen
authored
Merge pull request #2730 from MicrosoftDocs/master
3/16/2020 AM Publish
2 parents 7ecd91d + 2765b8c commit 6378472

File tree

379 files changed

+1040
-1439
lines changed

Some content is hidden

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

379 files changed

+1040
-1439
lines changed

‎docs/assembler/inline/even-and-align-directives.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "EVEN and ALIGN Directives"
33
ms.date: "08/30/2018"
4-
f1_keywords: ["align", "EVEN"]
54
helpviewer_keywords: ["EVEN directive", "directives, MASM", "MASM (Microsoft Macro Assembler), directives", "NOP (no operation instruction)", "ALIGN directive"]
65
ms.assetid: 7357ab2d-4a5c-43ca-accb-a5f21cdfcde5
76
---

‎docs/assembler/inline/type-and-variable-sizes-in-inline-assembly.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,6 @@
22
title: "Type and Variable Sizes in Inline Assembly"
33
ms.date: "08/30/2018"
44
ms.topic: "reference"
5-
f1_keywords: ["length", "Type"]
65
helpviewer_keywords: ["variables, length", "size, getting in inline assembly", "size", "LENGTH operator", "TYPE operator", "SIZE operator", "inline assembly, operators", "variables, type", "variables, size"]
76
ms.assetid: b62c2f2b-a7ad-4145-bae4-d890db86d348
87
---

‎docs/assembler/masm/dword.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "DWORD"
33
ms.date: "12/17/2019"
4-
f1_keywords: ["DWORD"]
54
helpviewer_keywords: ["DWORD directive"]
65
ms.assetid: 20efd7c6-1ee6-45a1-9feb-86ce7978142a
76
---

‎docs/assembler/masm/else-masm.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "ELSE (MASM)"
33
ms.date: "12/17/2019"
4-
f1_keywords: ["else"]
54
helpviewer_keywords: ["ELSE directive"]
65
ms.assetid: c43af707-4567-4489-97ca-f14982d84e88
76
---

‎docs/assembler/masm/extern-masm.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "EXTERN (MASM)"
33
ms.date: "12/06/2019"
4-
f1_keywords: ["extern"]
54
helpviewer_keywords: ["EXTERN directive"]
65
ms.assetid: 667d703d-3aaf-4139-a586-29bc5dab1aff
76
---

‎docs/assembler/masm/for-masm.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "FOR (MASM)"
33
ms.date: "12/17/2019"
4-
f1_keywords: ["for"]
54
helpviewer_keywords: ["FOR directive"]
65
ms.assetid: 99872e61-f503-4d34-b305-59f8556ba6b7
76
---

‎docs/assembler/masm/goto-masm.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "GOTO (MASM)"
33
ms.date: "12/16/2019"
4-
f1_keywords: ["goto"]
54
helpviewer_keywords: ["GOTO directive"]
65
ms.assetid: 6a5f73e7-6784-4eae-ac52-4fc77a7f369f
76
---

‎docs/assembler/masm/if-masm.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "IF (MASM)"
33
ms.date: "12/17/2019"
4-
f1_keywords: ["if"]
54
helpviewer_keywords: ["IF directive"]
65
ms.assetid: 82e43712-4f0c-4bf6-90ce-0663e81af707
76
---

‎docs/assembler/masm/include-masm.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "INCLUDE (MASM)"
33
ms.date: "12/17/2019"
4-
f1_keywords: ["include"]
54
helpviewer_keywords: ["INCLUDE directive"]
65
ms.assetid: 1c7964ee-715c-414e-a45e-74af93476eb4
76
---

‎docs/assembler/masm/name-masm.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "NAME (MASM)"
33
ms.date: "12/17/2019"
4-
f1_keywords: ["name"]
54
helpviewer_keywords: ["NAME directive"]
65
ms.assetid: 7a7ab431-6ffe-4293-9b76-4a5e020c66da
76
---

‎docs/assembler/masm/operator-and.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "operator AND"
33
ms.date: "12/17/2019"
4-
f1_keywords: ["And", "operator AND"]
4+
f1_keywords: ["operator AND"]
55
helpviewer_keywords: ["operator AND", "AND operator"]
66
ms.assetid: 6862d248-c169-4db8-a478-9d0ce4fdd1e3
77
---

‎docs/assembler/masm/operator-length.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "operator LENGTH"
33
ms.date: "12/17/2019"
4-
f1_keywords: ["operator LENGTH", "length"]
4+
f1_keywords: ["operator LENGTH"]
55
helpviewer_keywords: ["LENGTH operator", "operator LENGTH"]
66
ms.assetid: dee7ba98-8e91-4078-9435-a2c8506e37f2
77
---

‎docs/assembler/masm/operator-or.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "operator OR"
33
ms.date: "12/17/2019"
4-
f1_keywords: ["operator OR", "Or"]
54
helpviewer_keywords: ["operator OR", "OR operator, bitwise"]
65
ms.assetid: fab36ba6-8ee0-4778-beb9-21dce6d99db7
76
---

‎docs/assembler/masm/operator-type.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "operator TYPE"
33
ms.date: "12/17/2019"
4-
f1_keywords: ["Type", "operator TYPE"]
4+
f1_keywords: ["operator TYPE"]
55
helpviewer_keywords: ["operator TYPE", "TYPE operator"]
66
ms.assetid: 5e714381-4a58-4323-88f8-512b01b2e155
77
---

‎docs/assembler/masm/while-masm.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "WHILE (MASM)"
33
ms.date: "12/16/2019"
4-
f1_keywords: ["while"]
54
helpviewer_keywords: ["WHILE directive"]
65
ms.assetid: ff9d908e-7e7f-4983-9f6b-31ff51ef0fad
76
---

‎docs/atl-mfc-shared/memory-management-with-cstringt.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "Memory Management with CStringT"
33
ms.date: "11/04/2016"
4-
f1_keywords: ["CStringT", "ATL::CStringT", "ATL.CStringT"]
54
helpviewer_keywords: ["CString objects, memory management", "memory [C++], usage", "IAtlStringMgr class, using", "strings [C++], custom memory management", "CFixedStringT class, description of", "strings [C++], memory management", "CStringT class, memory management"]
65
ms.assetid: 88b8342d-19b5-48c4-9cf6-e4c44cece21e
76
---

‎docs/atl-mfc-shared/reference/ctime-class.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "CTime Class"
33
ms.date: "10/18/2018"
4-
f1_keywords: ["CTime", "ATLTIME/ATL::CTime", "ATLTIME/ATL::CTime::CTime", "ATLTIME/ATL::CTime::Format", "ATLTIME/ATL::CTime::FormatGmt", "ATLTIME/ATL::CTime::GetAsDBTIMESTAMP", "ATLTIME/ATL::CTime::GetAsSystemTime", "ATLTIME/ATL::CTime::GetCurrentTime", "ATLTIME/ATL::CTime::GetDay", "ATLTIME/ATL::CTime::GetDayOfWeek", "ATLTIME/ATL::CTime::GetGmtTm", "ATLTIME/ATL::CTime::GetHour", "ATLTIME/ATL::CTime::GetLocalTm", "ATLTIME/ATL::CTime::GetMinute", "ATLTIME/ATL::CTime::GetMonth", "ATLTIME/ATL::CTime::GetSecond", "ATLTIME/ATL::CTime::GetTime", "ATLTIME/ATL::CTime::GetYear", "ATLTIME/ATL::CTime::Serialize64"]
4+
f1_keywords: ["ATLTIME/ATL::CTime", "ATLTIME/ATL::CTime::CTime", "ATLTIME/ATL::CTime::Format", "ATLTIME/ATL::CTime::FormatGmt", "ATLTIME/ATL::CTime::GetAsDBTIMESTAMP", "ATLTIME/ATL::CTime::GetAsSystemTime", "ATLTIME/ATL::CTime::GetCurrentTime", "ATLTIME/ATL::CTime::GetDay", "ATLTIME/ATL::CTime::GetDayOfWeek", "ATLTIME/ATL::CTime::GetGmtTm", "ATLTIME/ATL::CTime::GetHour", "ATLTIME/ATL::CTime::GetLocalTm", "ATLTIME/ATL::CTime::GetMinute", "ATLTIME/ATL::CTime::GetMonth", "ATLTIME/ATL::CTime::GetSecond", "ATLTIME/ATL::CTime::GetTime", "ATLTIME/ATL::CTime::GetYear", "ATLTIME/ATL::CTime::Serialize64"]
55
helpviewer_keywords: ["CTime class", "shared classes, CTime"]
66
ms.assetid: 0a299544-485b-48dc-9d3c-fdc30f57d612
77
---

‎docs/build/configuring-programs-for-windows-xp.md

Lines changed: 29 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,46 @@
11
---
22
title: "Configuring Programs for Windows XP"
3-
ms.date: "05/16/2019"
3+
description: "How to install and use the C++ Windows XP toolsets in Visual Studio."
4+
ms.date: "03/16/2020"
45
ms.assetid: 1e4487b3-d815-4123-878b-5718b22f0fd5
56
---
67
# Configuring Programs for Windows XP
78

8-
Because Visual Studio supports multiple platform toolsets, you can target operating systems and runtime libraries that are not supported by the default toolset. For example, by switching the platform toolset, you can use the C++11, C++14, and C++17 language enhancements supported by the MSVC compiler in Visual Studio to create apps that target Windows XP and Windows Server 2003. You can also use older platform toolsets to maintain binary-compatible legacy code and still take advantage of the latest features of the Visual Studio IDE.
9+
Visual Studio supports multiple platform toolsets. That means it's possible to target operating systems and runtime libraries that aren't supported by the default toolset. For example, by switching the platform toolset, you can use the Visual Studio 2017 C++ compiler to create apps that target Windows XP and Windows Server 2003. You can also use older platform toolsets to maintain binary-compatible legacy code and still take advantage of the latest features of the Visual Studio IDE.
910

10-
Visual Studio 2019 and later does not include support for creating code for Windows XP by using the v142 toolset. Support for Windows XP development by using the v141 toolset that shipped in Visual Studio 2017 is available as an optional component in the Visual Studio Installer.
11+
::: moniker range="vs-2019"
12+
13+
The v142 toolset supplied in Visual Studio 2019 doesn't include support for creating code for Windows XP. Support for Windows XP development by using the Visual Studio 2017 v141_xp toolset is available as an individual component option in the Visual Studio Installer.
14+
15+
::: moniker-end
1116

1217
## Install the Windows XP platform toolset
1318

14-
To get the platform toolset and components to target Windows XP and Windows Server 2003 in Visual Studio 2017, run the Visual Studio Installer. When you initially install Visual Studio or when you choose **Modify** to modify an existing installation, make sure that the **Desktop development with C++** workload is selected. In the list of optional components for this workload, choose **Windows XP support for C++**, and then choose **Install** or **Modify**.
19+
::: moniker range="<=vs-2017"
20+
21+
To get the Visual Studio 2017 platform toolset and components to target Windows XP and Windows Server 2003, run the Visual Studio Installer. When you initially install Visual Studio or when you modify an existing installation, make sure the **Desktop development with C++** workload is selected. In the list of optional components for this workload, choose **Windows XP support for C++**, and then choose **Install** or **Modify**.
22+
23+
::: moniker-end
24+
25+
::: moniker range="vs-2019"
26+
27+
To get the v141_xp platform toolset and components to target Windows XP and Windows Server 2003, run the Visual Studio Installer. When you initially install Visual Studio, or when you modify an existing installation, make sure the **Desktop development with C++** workload is selected. In the **Individual components** tab, under **Compilers, build tools, and runtimes**, choose **C++ Windows XP Support for VS 2017 (v141) tools \[Deprecated]**, and then choose **Install** or **Modify**.
28+
29+
::: moniker-end
1530

1631
## Windows XP targeting experience
1732

18-
The Windows XP platform toolset that's included in Visual Studio is a version of the Windows 7 SDK, but it uses the current C++ compiler. It also configures project properties to appropriate default values, for example, the specification of a compatible linker for down-level targeting. Only Windows desktop apps that are created by using a Windows XP platform toolset run on Windows XP and Windows Server 2003, but those apps can also run on more recent Windows operating systems.
33+
The Windows XP platform toolset that's included in Visual Studio is a version of the Windows 7 SDK, but it uses the Visual Studio 2017 C++ compiler. It also configures project properties to appropriate default values, for example, the specification of a compatible linker for down-level targeting. Only Windows desktop apps created by using a Windows XP platform toolset can run on Windows XP and Windows Server 2003. Those apps can also run on more recent Windows operating systems.
1934

20-
#### To target Windows XP
35+
### To target Windows XP
2136

2237
1. In **Solution Explorer**, open the shortcut menu for your project, and then choose **Properties**.
2338

24-
1. In the **Property Pages** dialog box for the project, under **Configuration Properties** > **General**, set the **Platform Toolset** property to the desired Windows XP toolset. For example, choose **Visual Studio 2017 - Windows XP (v141_xp)** to create code for Windows XP and Windows Server 2003 by using the Microsoft C++ compiler in Visual Studio 2017.
39+
1. In the **Property Pages** dialog box for the project, select **Configuration Properties** > **General**. Set the **Platform Toolset** property to your preferred Windows XP toolset. For example, choose **Visual Studio 2017 - Windows XP (v141_xp)** to create code for Windows XP and Windows Server 2003 by using the Microsoft C++ compiler in Visual Studio 2017.
2540

2641
### C++ runtime support
2742

28-
Along with the Windows XP platform toolset, the C Runtime Library (CRT), C++ Standard Library, Active Template Library (ATL), Concurrency Runtime Library (ConCRT), Parallel Patterns Library (PPL), Microsoft Foundation Class Library (MFC), and C++ AMP (C++ Accelerated Massive Programming) library include runtime support for Windows XP and Windows Server 2003. For these operating systems, the minimum supported versions are Windows XP Service Pack 3 (SP3) for x86, Windows XP Service Pack 2 (SP2) for x64, and Windows Server 2003 Service Pack 2 (SP2) for both x86 and x64.
43+
Along with the Windows XP platform toolset, several libraries include runtime support for Windows XP and Windows Server 2003. These libraries are: the C Runtime Library (CRT), C++ Standard Library, Active Template Library (ATL), Concurrency Runtime Library (ConCRT), Parallel Patterns Library (PPL), Microsoft Foundation Class Library (MFC), and C++ AMP (C++ Accelerated Massive Programming) library. For these operating systems, the minimum supported versions are: Windows XP Service Pack 3 (SP3) for x86, Windows XP Service Pack 2 (SP2) for x64, and Windows Server 2003 Service Pack 2 (SP2) for both x86 and x64.
2944

3045
These libraries are supported by the platform toolsets installed by Visual Studio, depending on the target:
3146

@@ -43,24 +58,24 @@ These libraries are supported by the platform toolsets installed by Visual Studi
4358
4459
### Differences between the toolsets
4560

46-
Due to differences in platform and library support, the development experience for apps that use a Windows XP platform toolset is not as complete as for apps that use the default Visual Studio platform toolset.
61+
Because of differences in platform and library support, the development experience for apps that use a Windows XP platform toolset isn't as complete as for apps that use the default Visual Studio platform toolset.
4762

4863
- **C++ language features**
4964

50-
Only C++ language features implemented in Visual Studio 2012 are supported in apps that use the v110\_xp platform toolset. Only C++ language features implemented in Visual Studio 2013 are supported in apps that use the v120\_xp platform toolset. Only C++ language features implemented in Visual Studio 2015 are supported in apps that use the v140\_xp platform toolset. Visual Studio uses the corresponding compiler when it builds using the older platform toolsets. Use the most recent Windows XP platform toolset to take advantage of additional C++ language features implemented in that version of the compiler.
65+
Only C++ language features implemented in Visual Studio 2012 are supported in apps that use the v110\_xp platform toolset. Only C++ language features implemented in Visual Studio 2013 are supported in apps that use the v120\_xp platform toolset. Only C++ language features implemented in Visual Studio 2015 are supported in apps that use the v140\_xp platform toolset. Only C++ language features implemented in Visual Studio 2017 are supported in apps that use the v141\_xp platform toolset. Visual Studio uses the corresponding compiler when it builds using the older platform toolsets. Use the most recent Windows XP platform toolset to take advantage of additional C++ language features implemented in that version of the compiler.
5166

5267
- **Remote debugging**
5368

54-
Remote Tools for Visual Studio doesn't support remote debugging on Windows XP or Windows Server 2003. To debug an app when it's running on Windows XP or Windows Server 2003, you can use a debugger from an older version of Visual Studio to debug it locally or remotely. This resembles the experience of debugging an app on Windows Vista, which is a runtime target of the platform toolset, but not a remote debugging target.
69+
Remote Tools for Visual Studio doesn't support remote debugging on Windows XP or Windows Server 2003. To debug an app locally or remotely on Windows XP or Windows Server 2003, use a debugger from an older version of Visual Studio. It's similar to debugging an app on Windows Vista, which is a runtime target of the platform toolset, but not a remote debugging target.
5570

5671
- **Static analysis**
5772

58-
The Windows XP platform toolsets don't support static analysis because the SAL annotations for the Windows 7 SDK and the runtime libraries are incompatible. When you want to perform static analysis on an app that supports Windows XP or Windows Server 2003, you can temporarily switch the solution to target the default platform toolset to perform the analysis, and then switch back to the Windows XP platform toolset to build the app.
73+
The Windows XP platform toolsets don't support static analysis because the SAL annotations for the Windows 7 SDK and the runtime libraries are incompatible. You can still perform static analysis on an app that supports Windows XP or Windows Server 2003. Temporarily switch the solution to target the default platform toolset for the analysis, and then switch back to the Windows XP platform toolset to build the app.
5974

6075
- **Debugging of DirectX graphics**
6176

62-
Because the Graphics Debugger does not support the Direct3D 9 API, it cannot be used to debug apps that use Direct3D on Windows XP or Windows Server 2003. However, if the app implements an alternative renderer that uses the Direct3D 10 or Direct3D 11 APIs, the Graphics Debugger can be used to diagnose problems with the use of those APIs.
77+
Because the Graphics Debugger doesn't support the Direct3D 9 API, it can't be used to debug apps that use Direct3D on Windows XP or Windows Server 2003. However, if the app implements an alternative renderer based on Direct3D 10 or Direct3D 11 APIs, you can use the Graphics Debugger to diagnose problems.
6378

6479
- **Building HLSL**
6580

66-
By default, the Windows XP toolset does not compile HLSL source code files. To compile HLSL files, download and install the June 2010 DirectX SDK, and then set the project's VC directories to include it. For more information, see the "DirectX SDK Does Not Register Include/Library Paths with Visual Studio 2010" section of the [June 2010 DirectX SDK download page](https://www.microsoft.com/download/details.aspx?displaylang=en&id=6812).
81+
The Windows XP toolset doesn't compile HLSL source code files by default. To compile HLSL files, download and install the June 2010 DirectX SDK, and then set the project's VC directories to include it. For more information, see the "DirectX SDK Does Not Register Include/Library Paths with Visual Studio 2010" section of the [June 2010 DirectX SDK download page](https://www.microsoft.com/download/details.aspx?displaylang=en&id=6812).

‎docs/build/cppproperties-schema-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ A configuration may have any of the following properties:
2222
|`forcedInclude`|Header to be automatically included in every compilation unit (maps to /FI for MSVC or -include for clang)|
2323
|`undefines`|The list of macros to be undefined (maps to /U for MSVC)|
2424
|`intelliSenseMode`|The IntelliSense engine to be used. You can specify one of the predefined architecture-specific variants for MSVC, gcc, or Clang.|
25-
|`environments`|User-defined sets of variables that behave like environment variables in a command prompt and are accessed with the ${env.<VARIABLE>} macro.|
25+
|`environments`|User-defined sets of variables that behave like environment variables in a command prompt and are accessed with the ${env.\<VARIABLE>} macro.|
2626

2727
### intelliSenseMode values
2828

‎docs/build/exporting-from-a-dll-using-declspec-dllexport.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Exporting from a DLL Using __declspec(dllexport)"
33
ms.date: "05/06/2019"
4-
f1_keywords: ["dllexport", "__declspec"]
4+
f1_keywords: ["dllexport"]
55
helpviewer_keywords: ["__declspec(dllexport) keyword [C++]", "names [C++], DLL exports by", "export directives [C++]", "exporting DLLs [C++], __declspec(dllexport) keyword"]
66
ms.assetid: a35e25e8-7263-4a04-bad4-00b284458679
77
---

‎docs/build/importing-data-using-declspec-dllimport.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "Importing Data Using __declspec(dllimport)"
33
ms.date: "11/04/2016"
4-
f1_keywords: ["dllimport"]
54
helpviewer_keywords: ["importing data [C++]", "dllimport attribute [C++], data imports", "__declspec(dllimport) keyword [C++]", "importing DLLs [C++], __declspec(dllimport)"]
65
ms.assetid: 0ae70b39-87c7-4181-8be9-e786e0db60b0
76
---

‎docs/build/importing-function-calls-using-declspec-dllimport.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "Importing Function Calls Using __declspec(dllimport)"
33
ms.date: "11/04/2016"
4-
f1_keywords: ["__declspec", "dllimport"]
54
helpviewer_keywords: ["importing function calls [C++]", "dllimport attribute [C++], function call imports", "__declspec(dllimport) keyword [C++]", "function calls [C++], importing"]
65
ms.assetid: 6b53c616-0c6d-419a-8e2a-d2fff20510b3
76
---

‎docs/build/importing-into-an-application-using-declspec-dllimport.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: "Import into an application using __declspec(dllimport)"
33
ms.date: "11/04/2016"
4-
f1_keywords: ["__declspec", "dllimport"]
54
helpviewer_keywords: ["__declspec(dllimport) keyword [C++]", "importing DLLs [C++], __declspec(dllimport)"]
65
ms.assetid: edb4da4e-f83a-44cf-a668-9239d49dbe42
76
---

‎docs/build/reference/allowbind.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "/ALLOWBIND"
33
ms.date: "11/04/2016"
4-
f1_keywords: ["/allowbind"]
4+
f1_keywords: ["/allowbind_bind"]
55
helpviewer_keywords: ["ALLOWBIND editbin option", "/ALLOWBIND editbin option", "-ALLOWBIND editbin option"]
66
ms.assetid: eaadbb8c-4339-4281-9a75-3a1ce2352ff8
77
---

‎docs/build/reference/allowisolation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "/ALLOWISOLATION"
33
ms.date: "11/04/2016"
4-
f1_keywords: ["/ALLOWISOLATION"]
4+
f1_keywords: ["/ALLOWISOLATION_EDITBIN"]
55
helpviewer_keywords: ["-ALLOWISOLATION editbin option", "/ALLOWISOLATION editbin option", "ALLOWISOLATION editbin option"]
66
ms.assetid: 91430344-f64f-491a-a5a5-7ea3b21cbe68
77
---

0 commit comments

Comments
 (0)