Skip to content

Commit c90fd0e

Browse files
Colin Robertsonmikeblome
Colin Robertson
authored and
mikeblome
committed
Fixes for various FWLINK errors and related issues (MicrosoftDocs#494)
1 parent 1fe358c commit c90fd0e

146 files changed

Lines changed: 614 additions & 613 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/arm/arm-assembler-command-line-reference.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ armasm [[options]] -o objectfile sourcefile
3737
Add the specified directories to the include search path.
3838

3939
-predefine `directive`
40-
Specify a SETA, SETL, or SETS directive to predefine a symbol. Example: **armasm.exe -predefine "COUNT SETA 150" source.asm**. For more information, see the [ARM assembler tools guide](http://go.microsoft.com/fwlink/?LinkId=246102).
40+
Specify a SETA, SETL, or SETS directive to predefine a symbol. Example: **armasm.exe -predefine "COUNT SETA 150" source.asm**. For more information, see the [ARM assembler tools guide](http://go.microsoft.com/fwlink/p/?linkid=246102).
4141

4242
-nowarn
4343
Disable all warning messages.

‎docs/assembler/arm/arm-assembler-diagnostic-messages.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ filename(lineno) : [error|warning] Anum: message
2929

3030
### Errors
3131
A2193: this instruction generates unpredictable behavior
32-
The ARM architecture cannot guarantee what happens when this instruction is executed. For details about the well-defined forms of this instruction, consult the [ARM Architecture Reference Manual](http://go.microsoft.com/fwlink/?LinkId=246464).
32+
The ARM architecture cannot guarantee what happens when this instruction is executed. For details about the well-defined forms of this instruction, consult the [ARM Architecture Reference Manual](http://go.microsoft.com/fwlink/p/?linkid=246464).
3333

3434
```
3535
@@ -111,7 +111,7 @@ ANDS r0, r0, #4, #2 ; A4508: Use of this rotated constant is deprecat
111111
```
112112

113113
A4509: This form of conditional instruction is deprecated
114-
This form of conditional instruction has been deprecated by ARM in the ARMv8 architecture. We recommend that you change the code to use conditional branches. To see which conditional instructions are still supported, consult the [ARM Architecture Reference Manual](http://go.microsoft.com/fwlink/?LinkId=246464).
114+
This form of conditional instruction has been deprecated by ARM in the ARMv8 architecture. We recommend that you change the code to use conditional branches. To see which conditional instructions are still supported, consult the [ARM Architecture Reference Manual](http://go.microsoft.com/fwlink/p/?linkid=246464).
115115

116116
This warning is not emitted when the `-oldit` command-line switch is used.
117117

‎docs/assembler/arm/arm-assembler-directives.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,13 @@ manager: "ghogen"
1616
ms.workload: ["cplusplus"]
1717
---
1818
# ARM Assembler Directives
19-
For the most part, the Microsoft ARM assembler uses the ARM assembly language, which is documented in Chapter 7 of the [ARM assembler tools guide](http://go.microsoft.com/fwlink/?LinkId=246102). However, the Microsoft implementations of some assembly directives differ from the ARM assembly directives. This article explains the differences.
19+
For the most part, the Microsoft ARM assembler uses the ARM assembly language, which is documented in Chapter 7 of the [ARM assembler tools guide](http://go.microsoft.com/fwlink/p/?linkid=246102). However, the Microsoft implementations of some assembly directives differ from the ARM assembly directives. This article explains the differences.
2020

2121
## Microsoft Implementations of ARM Assembly Directives
2222
AREA
2323
The Microsoft ARM assembler supports these AREA attributes: ALIGN, CODE, CODEALIGN, DATA, NOINIT, READONLY, READWRITE, THUMB, ARM.
2424

25-
All except THUMB and ARM work as documented in the [ARM assembler tools guide](http://go.microsoft.com/fwlink/?LinkId=246102).
25+
All except THUMB and ARM work as documented in the [ARM assembler tools guide](http://go.microsoft.com/fwlink/p/?linkid=246102).
2626

2727
In the Microsoft ARM assembler, THUMB indicates that a CODE section contains Thumb code, and is the default for CODE sections. ARM indicates that the section contains ARM code.
2828

‎docs/assembler/masm/dot-model.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ Initializes the program memory model.
5252
|`stackoption`|Not used|`NEARSTACK`, `FARSTACK`|
5353

5454
## Code
55-
For MASM-related samples, download the Compiler samples from [Visual C++ Samples and Related Documentation for Visual Studio 2010](http://go.microsoft.com/fwlink/?LinkID=178749).
55+
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).
5656

5757
The following example demonstrates the use of the `.MODEL` directive.
5858

@@ -90,4 +90,4 @@ end
9090

9191
## See Also
9292
[Directives Reference](../../assembler/masm/directives-reference.md)
93-
[Visual C++ Samples and Related Documentation for Visual Studio 2010](http://go.microsoft.com/fwlink/?LinkID=178749)
93+
[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
@@ -442,7 +442,7 @@ inline BOOL SetFileAttributes(LPCTSTR lpFileName, DWORD dwAttributes);
442442
The name of the file or directory.
443443

444444
`dwAttributes`
445-
The file attributes to set for the file. For more information, see [SetFileAttributesTransacted](http://go.microsoft.com/fwlink/linkid=158699).
445+
The file attributes to set for the file. For more information, see [SetFileAttributesTransacted](http://go.microsoft.com/fwlink/p/?linkid=158699).
446446

447447
### Remarks
448448
This wrapper calls the `SetFileAttributesTransacted` function.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -195,7 +195,7 @@ addrinfo* const GetAddrInfoList() const;
195195
```
196196

197197
### Return Value
198-
Pointer to a linked list of one or more `addrinfo` structures containing response information about the host. For more information about the `addrinfo` structure, see the "addrinfo" article in the [MSDN Library](http://go.microsoft.com/fwlink/linkid=556)
198+
Pointer to a linked list of one or more `addrinfo` structures containing response information about the host. For more information, see [addrinfo structure](https://msdn.microsoft.com/library/windows/desktop/ms737530).
199199

200200
## See Also
201201
[Class Overview](../../atl/atl-class-overview.md)

‎docs/build/building-on-the-command-line.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The command prompt shortcuts are installed in a version-specific [!INCLUDE[vsprv
3939

4040
The actual Start menu folder and shortcut names vary depending on the version of [!INCLUDE[vsprvs](../assembler/masm/includes/vsprvs_md.md)] you have installed, and the installation Nickname if you set one. For example, if you have Visual Studio 2017 installed, and you've given it an installation Nickname of 15.3, the developer command prompt shortcut is named **Developer Command Prompt for VS 2017 (15.3)**, in a folder named **Visual Studio 2017**.
4141

42-
If you've installed the [Build Tools for Visual Studio 2017](https://go.microsoft.com/fwlink/?linkid=840931) or [Visual C++ 2015 Build Tools](http://landinghub.visualstudio.com/visual-cpp-build-tools) edition, there may only be specific native or cross tools developer command prompt options.
42+
If you've installed the [Build Tools for Visual Studio 2017](https://go.microsoft.com/fwlink/p/?linkid=840931) or [Visual C++ 2015 Build Tools](http://landinghub.visualstudio.com/visual-cpp-build-tools) edition, there may only be specific native or cross tools developer command prompt options.
4343

4444
<a name="developer_command_prompt"></a>
4545
## To open a developer command prompt window

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.workload: ["cplusplus"]
1919
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 Visual C++ compiler in Visual Studio to create apps that target [!INCLUDE[winxp](../build/includes/winxp_md.md)] and [!INCLUDE[WinXPSvr](../build/includes/winxpsvr_md.md)]. 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.
2020

2121
> [!NOTE]
22-
> If you are using [!INCLUDE[vs_dev11_long](../build/includes/vs_dev11_long_md.md)], you must install [!INCLUDE[vs_dev11_long](../build/includes/vs_dev11_long_md.md)] Update 4 to add platform toolset support for [!INCLUDE[winxp](../build/includes/winxp_md.md)] and [!INCLUDE[WinXPSvr](../build/includes/winxpsvr_md.md)]. To download and install a copy of [!INCLUDE[vs_dev11_long](../build/includes/vs_dev11_long_md.md)] Update 4, see [Microsoft Visual Studio Express 2012 for Windows Desktop](http://go.microsoft.com/fwlink/?LinkID=265464) in the Microsoft Download Center. Then install [Visual Studio 2012 Update 4](http://go.microsoft.com/fwlink/?LinkID=335900) to get the v110_xp platform toolset. Use Windows Update to receive the latest software updates after installation.
22+
> If you are using [!INCLUDE[vs_dev11_long](../build/includes/vs_dev11_long_md.md)], you must install [!INCLUDE[vs_dev11_long](../build/includes/vs_dev11_long_md.md)] Update 4 to add platform toolset support for [!INCLUDE[winxp](../build/includes/winxp_md.md)] and [!INCLUDE[WinXPSvr](../build/includes/winxpsvr_md.md)]. To download and install a copy of [!INCLUDE[vs_dev11_long](../build/includes/vs_dev11_long_md.md)] Update 4, see [Microsoft Visual Studio Express 2012 for Windows Desktop](http://go.microsoft.com/fwlink/p/?linkid=265464) in the Microsoft Download Center. Then install [Visual Studio 2012 Update 4](http://go.microsoft.com/fwlink/p/?linkid=335900) to get the v110_xp platform toolset. Use Windows Update to receive the latest software updates after installation.
2323
2424
## Windows XP targeting experience
2525
The Windows XP platform toolset that's included in Visual Studio is a version of the [!INCLUDE[win7](../build/includes/win7_md.md)] SDK that was included in [!INCLUDE[vs_dev10_long](../build/includes/vs_dev10_long_md.md)], 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 the Windows XP platform toolset run on [!INCLUDE[winxp](../build/includes/winxp_md.md)] and [!INCLUDE[WinXPSvr](../build/includes/winxpsvr_md.md)], but those apps can also run on more recent Windows operating systems.

‎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
@@ -22,7 +22,7 @@ You can add custom tool options to the Visual Studio **Property Pages** window b
2222

2323
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*.
2424

25-
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/?LinkID=191489) on the Visual Studio Project Team blog.
25+
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.
2626

2727
### To add or change project properties
2828

‎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
@@ -28,7 +28,7 @@ You can change Visual C++ project settings to target different versions of the .
2828
> [!NOTE]
2929
> 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.
3030
31-
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/?LinkId=196619) on the Visual C++ blog.
31+
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.
3232

3333
### To change the target Framework
3434

0 commit comments

Comments
 (0)