Skip to content

Commit 5659184

Browse files
author
mikeblome
committed
converted fwlinks and added a missing AMP function
1 parent 2273faf commit 5659184

68 files changed

Lines changed: 163 additions & 165 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/assembler/masm/dot-model.md‎

Lines changed: 14 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
1-
---
2-
title: ".MODEL | Microsoft Docs"
3-
ms.custom: ""
4-
ms.date: "11/04/2016"
5-
ms.technology: ["cpp-masm"]
6-
ms.topic: "reference"
7-
f1_keywords: [".MODEL"]
8-
dev_langs: ["C++"]
9-
helpviewer_keywords: [".MODEL directive"]
10-
ms.assetid: 057f00df-1515-4c55-852a-d936c8a34b53
11-
author: "corob-msft"
12-
ms.author: "corob"
13-
ms.workload: ["cplusplus"]
1+
---
2+
title: ".MODEL | Microsoft Docs"
3+
ms.custom: ""
4+
ms.date: "11/04/2016"
5+
ms.technology: ["cpp-masm"]
6+
ms.topic: "reference"
7+
f1_keywords: [".MODEL"]
8+
dev_langs: ["C++"]
9+
helpviewer_keywords: [".MODEL directive"]
10+
ms.assetid: 057f00df-1515-4c55-852a-d936c8a34b53
11+
author: "corob-msft"
12+
ms.author: "corob"
13+
ms.workload: ["cplusplus"]
1414
---
1515
# .MODEL
1616
Initializes the program memory model.
@@ -47,7 +47,7 @@ Initializes the program memory model.
4747
|`stackoption`|Not used|`NEARSTACK`, `FARSTACK`|
4848

4949
## Code
50-
For MASM-related samples, download the Compiler samples from [Visual C++ Samples and Related Documentation for Visual Studio 2010](http://go.microsoft.com/fwlink/p/?linkid=178749).
50+
For MASM-related samples, download the Compiler samples from [Visual C++ Samples](https://github.com/Microsoft/VCSamples) on GitHub.
5151

5252
The following example demonstrates the use of the `.MODEL` directive.
5353

@@ -85,4 +85,3 @@ end
8585

8686
## See Also
8787
[Directives Reference](../../assembler/masm/directives-reference.md)
88-
[Visual C++ Samples and Related Documentation for Visual Studio 2010](http://go.microsoft.com/fwlink/p/?linkid=178749)

‎docs/atl/reference/catltransactionmanager-class.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -437,7 +437,7 @@ inline BOOL SetFileAttributes(LPCTSTR lpFileName, DWORD dwAttributes);
437437
The name of the file or directory.
438438

439439
*dwAttributes*
440-
The file attributes to set for the file. For more information, see [SetFileAttributesTransacted](http://go.microsoft.com/fwlink/p/?linkid=158699).
440+
The file attributes to set for the file. For more information, see [SetFileAttributesTransacted](/windows/desktop/api/winbase/nf-winbase-setfileattributestransacteda).
441441

442442
### Remarks
443443
This wrapper calls the `SetFileAttributesTransacted` function.

‎docs/build/freelibrary-and-afxfreelibrary.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.author: "corob"
1313
ms.workload: ["cplusplus"]
1414
---
1515
# FreeLibrary and AfxFreeLibrary
16-
Processes that explicitly link to a DLL call the [FreeLibrary](http://go.microsoft.com/fwlink/p/?LinkID=259188) function when the DLL module is no longer needed. This function decrements the module's reference count and, if the reference count is zero, unmaps it from the address space of the process.
16+
Processes that explicitly link to a DLL call the [FreeLibrary](https://msdn.microsoft.com/library/windows/desktop/ms683152(v=vs.85).aspx) function when the DLL module is no longer needed. This function decrements the module's reference count and, if the reference count is zero, unmaps it from the address space of the process.
1717

1818
In an MFC application, use [AfxFreeLibrary](../mfc/reference/application-information-and-management.md#afxfreelibrary) instead of `FreeLibrary` to unload an MFC extension DLL. The interface (function prototype) for `AfxFreeLibrary` is the same as `FreeLibrary`.
1919

@@ -31,5 +31,5 @@ Processes that explicitly link to a DLL call the [FreeLibrary](http://go.microso
3131

3232
## See Also
3333
[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
34-
[FreeLibrary](http://go.microsoft.com/fwlink/p/?LinkID=259188)
34+
[FreeLibrary](https://msdn.microsoft.com/library/windows/desktop/ms683152(v=vs.85).aspx)
3535
[AfxFreeLibrary](../mfc/reference/application-information-and-management.md#afxfreelibrary)

‎docs/build/how-to-integrate-custom-tools-into-the-project-properties.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ You can add custom tool options to the Visual Studio **Property Pages** window b
1717

1818
The **Configuration Properties** section of the **Property Pages** window displays setting groups that are known as *rules*. Every rule contains the settings for a tool or a group of features. For example, the **Linker** rule contains the settings for the linker tool. The settings in a rule can be subdivided into *categories*.
1919

20-
This document explains how to create a file in a set directory that contains properties for your custom tool so that the properties are loaded when Visual Studio starts. For information about how to modify the file, see [Platform Extensibilty Part 2](http://go.microsoft.com/fwlink/p/?linkid=191489) on the Visual Studio Project Team blog.
20+
This document explains how to create a file in a set directory that contains properties for your custom tool so that the properties are loaded when Visual Studio starts. For information about how to modify the file, see [Platform Extensibilty Part 2](https://blogs.msdn.microsoft.com/vsproject/2009/06/18/platform-extensibility-part-2/) on the Visual Studio Project Team blog.
2121

2222
### To add or change project properties
2323

‎docs/build/how-to-modify-the-target-framework-and-platform-toolset.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ You can change Visual C++ project settings to target different versions of the .
2323
> [!NOTE]
2424
> To change the target platform toolset, you must have the associated version of Visual Studio or the Windows Platform SDK installed. For example, to target the Itanium platform with the **Windows7.1SDK** platform toolset, you must have [Microsoft Windows SDK for Windows 7 and .NET Framework 4 SP1](http://www.microsoft.com/download/details.aspx?id=8279) installed; however, you could use another compatible version of Visual Studio to do your development work, provided that you target the correct Framework version and platform toolset.
2525
26-
You can extend the target platform further by creating a custom platform toolset. For more information, see [C++ Native Multi-Targeting](http://go.microsoft.com/fwlink/p/?linkid=196619) on the Visual C++ blog.
26+
You can extend the target platform further by creating a custom platform toolset. For more information, see [C++ Native Multi-Targeting](https://blogs.msdn.microsoft.com/vcblog/2009/12/08/c-native-multi-targeting/) on the Visual C++ blog.
2727

2828
### To change the target Framework
2929

‎docs/build/loadlibrary-and-afxloadlibrary.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.workload: ["cplusplus"]
1414
---
1515
# LoadLibrary and AfxLoadLibrary
1616

17-
Processes call [LoadLibrary](https://go.microsoft.com/fwlink/p/?LinkID=259187) (or [AfxLoadLibrary](../mfc/reference/application-information-and-management.md#afxloadlibrary)) to explicitly link to a DLL. If the function succeeds, it maps the specified DLL into the address space of the calling process and returns a handle to the DLL that can be used with other functions in explicit linking—for example, `GetProcAddress` and `FreeLibrary`.
17+
Processes call [LoadLibraryExA](/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibraryexa) or [LoadLibraryExW](/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibraryexw)(or [AfxLoadLibrary](../mfc/reference/application-information-and-management.md#afxloadlibrary)) to explicitly link to a DLL. If the function succeeds, it maps the specified DLL into the address space of the calling process and returns a handle to the DLL that can be used with other functions in explicit linking—for example, `GetProcAddress` and `FreeLibrary`.
1818

1919
`LoadLibrary` attempts to locate the DLL by using the same search sequence that is used for implicit linking. If the system cannot find the DLL or if the entry-point function returns FALSE, `LoadLibrary` returns NULL. If the call to `LoadLibrary` specifies a DLL module that is already mapped into the address space of the calling process, the function returns a handle of the DLL and increments the reference count of the module.
2020

@@ -44,5 +44,3 @@ If Windows cannot load the DLL, the process can attempt to recover from the erro
4444
## See also
4545

4646
- [DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
47-
- [LoadLibrary](https://go.microsoft.com/fwlink/p/?LinkID=259187)
48-
- [AfxLoadLibrary](../mfc/reference/application-information-and-management.md#afxloadlibrary)

‎docs/build/reference/appcontainer.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,4 +25,4 @@ Marks an executable that must run in an app container—for example, a Microsoft
2525

2626
## See Also
2727
[EDITBIN Options](../../build/reference/editbin-options.md)
28-
[What's a Universal Windows App?](http://go.microsoft.com/fwlink/p/?LinkID=522074)
28+
[What's a Universal Windows App?](/windows/uwp/get-started/universal-application-platform-guide)

‎docs/build/reference/clr-common-language-runtime-compilation.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,7 @@ Enables applications and components to use features from the common language run
5050
Before Visual C++ 2005, **/clr:noAssembly** required **/LD**. **/LD** is now implied when you specify **/clr:noAssembly**.
5151

5252
**/clr:initialAppDomain**
53-
Enables a Visual C++ application to run on version 1 of the CLR. If you use **initialAppDomain**, then you may see some of the problems that are discussed in [BUG: AppDomainUnloaded exception when you use managed extensions for Visual C++ components](http://go.microsoft.com/fwlink/p/?linkid=169465) on the Microsoft Support Web site.
54-
55-
An application that is compiled by using **initialAppDomain** should not be used by an application that uses ASP.NET because it is not supported in version 1 of the CLR.
53+
Enables a Visual C++ application to run on version 1 of the CLR. An application that is compiled by using **initialAppDomain** should not be used by an application that uses ASP.NET because it is not supported in version 1 of the CLR.
5654

5755
**/clr:nostdlib**
5856
Instructs the compiler to ignore the default \clr directory. The compiler produces errors if you are including multiple versions of a DLL such as System.dll. Using this option lets you specify the specific framework to use during compilation.

‎docs/build/reference/debugtype-debug-info-options.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,10 +34,10 @@ The /DEBUGTYPE option specifies the types of debugging information generated by
3434
## Remarks
3535
Use the **/DEBUGTYPE** option to specify inclusion of relocation table data or .pdata and .xdata header information in the debugging stream. This causes the linker to include information about user-mode code that is visible in a kernel debugger when breaking in kernel-mode code. To make debugging symbols available when **FIXUP** is specified, include the **CV** argument.
3636

37-
To debug code in user mode, which is typical for applications, the **/DEBUGTYPE** option isn't needed. By default, the compiler switches that specify debugging output ([/Z7, /Zi, /ZI](../../build/reference/z7-zi-zi-debug-information-format.md)) emit all the information needed by the Visual Studio debugger. Use **/DEBUGTYPE:PDATA** or **/DEBUGTYPE:CV,PDATA,FIXUP** to debug code that combines user-mode and kernel-mode components, such as a configuration app for a device driver. For more information about kernel mode debuggers, see [Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)](http://go.microsoft.com/fwlink/p?LinkID=285651)
37+
To debug code in user mode, which is typical for applications, the **/DEBUGTYPE** option isn't needed. By default, the compiler switches that specify debugging output ([/Z7, /Zi, /ZI](../../build/reference/z7-zi-zi-debug-information-format.md)) emit all the information needed by the Visual Studio debugger. Use **/DEBUGTYPE:PDATA** or **/DEBUGTYPE:CV,PDATA,FIXUP** to debug code that combines user-mode and kernel-mode components, such as a configuration app for a device driver. For more information about kernel mode debuggers, see [Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)](/windows-hardware/drivers/debugger/index)
3838

3939
## See Also
4040
[/DEBUG (Generate Debug Info)](../../build/reference/debug-generate-debug-info.md)
4141
[/DRIVER (Windows NT Kernel Mode Driver)](../../build/reference/driver-windows-nt-kernel-mode-driver.md)
4242
[/PROFILE (Performance Tools Profiler)](../../build/reference/profile-performance-tools-profiler.md)
43-
[Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)](http://go.microsoft.com/fwlink/p?LinkID=285651)
43+
[Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)](/windows-hardware/drivers/debugger/index)

‎docs/build/reference/dependentloadflag.md‎

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,17 +24,17 @@ Sets the default load flags used when `LoadLibrary` is used to load DLLs.
2424

2525
|||
2626
|-|-|
27-
*loadflags*|An optional "C"-style 16-bit integer value in decimal, octal with a leading zero, or hexadecimal with a leading `0x`, that specifies the dependent load flags to apply to all [LoadLibrary](https://go.microsoft.com/fwlink/p/?LinkID=259187) calls. The default value is 0.
27+
*loadflags*|An optional "C"-style 16-bit integer value in decimal, octal with a leading zero, or hexadecimal with a leading `0x`, that specifies the dependent load flags to apply to all [LoadLibrary](/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibraryexa) calls. The default value is 0.
2828

2929
## Remarks
3030

3131
This option is new in Visual Studio 2017, and applies only to apps running on Windows 10 RS1 and later versions. This option is ignored by other operating systems that run the app.
3232

33-
On supported operating systems, this option has the effect of changing calls to `LoadLibrary("dependent.dll")` to the equivalent of `LoadLibraryEx("dependent.dll", 0, loadflags)`. Calls to [LoadLibraryEx](https://go.microsoft.com/fwlink/p/?LinkID=236091) are unaffected. This option does not apply recursively to DLLs loaded by your app.
33+
On supported operating systems, this option has the effect of changing calls to `LoadLibrary("dependent.dll")` to the equivalent of `LoadLibraryEx("dependent.dll", 0, loadflags)`. Calls to [LoadLibraryEx](/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibraryexa) are unaffected. This option does not apply recursively to DLLs loaded by your app.
3434

3535
This flag can be used to prevent DLL planting attacks. For example, if an app uses `LoadLibrary` to load a dependent DLL, an attacker could plant a DLL with the same name in the search path used by `LoadLibrary`, such as the current directory, which may be checked before system directories if safe DLL search mode is disabled. Safe DLL search mode places the user's current directory later in the search order, and is enabled by default on Windows XP SP2 and later versions. For more information, see [Dynamic-Link Library Search Order](/windows/desktop/Dlls/dynamic-link-library-search-order).
3636

37-
If you specify the link option `/DEPENDENTLOADFLAG:0xA00` (the value of the combined flags `LOAD_LIBRARY_SEARCH_APPLICATION_DIR | LOAD_LIBRARY_SEARCH_SYSTEM32`), then even if safe DLL search mode is disabled on the user's computer, the DLL search path is limited to protected directories that are more difficult for an attacker to change. For information on the flags available, and their symbolic and numeric values, see the *dwFlags* parameter description in [LoadLibraryEx](https://go.microsoft.com/fwlink/p/?LinkID=236091).
37+
If you specify the link option `/DEPENDENTLOADFLAG:0xA00` (the value of the combined flags `LOAD_LIBRARY_SEARCH_APPLICATION_DIR | LOAD_LIBRARY_SEARCH_SYSTEM32`), then even if safe DLL search mode is disabled on the user's computer, the DLL search path is limited to protected directories that are more difficult for an attacker to change. For information on the flags available, and their symbolic and numeric values, see the *dwFlags* parameter description in [LoadLibraryEx](/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibraryexa).
3838

3939
### To set the DEPENDENTLOADFLAG linker option in the Visual Studio development environment
4040

@@ -54,6 +54,5 @@ If you specify the link option `/DEPENDENTLOADFLAG:0xA00` (the value of the comb
5454
- [Linker Options](linker-options.md)
5555
- [How to link implicitly to a DLL](../linking-an-executable-to-a-dll.md#linking-implicitly)
5656
- [Determine which linking method to use](../linking-an-executable-to-a-dll.md#determining-which-linking-method-to-use)
57-
- [LoadLibrary](https://go.microsoft.com/fwlink/p/?LinkID=259187)
58-
- [LoadLibraryEx](https://go.microsoft.com/fwlink/p/?LinkID=236091)
57+
- [LoadLibraryEx](/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibraryexa)
5958
- [Dynamic-Link Library Search Order](/windows/desktop/Dlls/dynamic-link-library-search-order)

0 commit comments

Comments
 (0)