Skip to content

Commit 14c280d

Browse files
authored
Add "Remarks" heading for error references in range [C1801, C2000]
1 parent b93555b commit 14c280d

File tree

8 files changed

+16
-0
lines changed

8 files changed

+16
-0
lines changed

docs/error-messages/compiler-errors-1/fatal-error-c1852.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ ms.assetid: fa011004-b8d6-46f1-ba80-4785e4ce137f
1010

1111
> 'filename' is not a valid precompiled header file
1212
13+
## Remarks
14+
1315
The file is not a precompiled header.
1416

1517
### To fix by checking the following possible causes

docs/error-messages/compiler-errors-1/fatal-error-c1853.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ ms.assetid: ceb9b4a5-92bf-4573-8a9f-3109cc7743ce
1010

1111
> '*filename*' precompiled header file is from a previous version of the compiler, or the precompiled header is C++ and you are using it from C (or vice versa)
1212
13+
## Remarks
14+
1315
Possible causes:
1416

1517
- The precompiled header was compiled with a previous compiler version. Try recompiling the header with the current compiler.

docs/error-messages/compiler-errors-1/fatal-error-c1854.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ ms.assetid: 8c21a9cc-1737-475c-9e57-8725cd8937c1
1010

1111
> cannot overwrite information formed during creation of the precompiled header in object file: '*filename*'
1212
13+
## Remarks
14+
1315
You specified the [/Yu (Use Precompiled Header File)](../../build/reference/yu-use-precompiled-header-file.md) option after specifying the [/Yc (Create Precompiled Header File)](../../build/reference/yc-create-precompiled-header-file.md) option for the same file.
1416

1517
To fix this issue, in general, set only one file in your project to be compiled by using the **/Yc** option, and set all other files to compile by using the **/Yu** option. For details on the use of the **/Yc** option, and how to set it in the Visual Studio IDE, see [/Yc (Create Precompiled Header File)](../../build/reference/yc-create-precompiled-header-file.md). For more information on using precompiled headers, see [Creating Precompiled Header Files](../../build/creating-precompiled-header-files.md).

docs/error-messages/compiler-errors-1/fatal-error-c1900.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ ms.assetid: 3aaa583b-4c1a-45de-aa34-527d806f2cb5
1010

1111
> Il mismatch between '*tool1*' version '*number1*' and '*tool2*' version '*number2*'
1212
13+
## Remarks
14+
1315
Tools run in various passes of the compiler do not match. *number1* and *number2* refer to the dates on the files. For example, in pass 1, the compiler front end runs (c1.dll) and in pass 2, the compiler back end runs (c2.dll). The dates on the files must match.
1416

1517
To fix this issue, make sure that all updates have been applied to Visual Studio. If the problem persists, use **Programs and Features** in the Windows Control Panel to repair or reinstall Visual Studio.

docs/error-messages/compiler-errors-1/fatal-error-c1902.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ ms.assetid: 2dc066cc-fcb1-4725-8bcb-9f44dd0905b7
1010

1111
> program database manager mismatch; please check your installation
1212
13+
## Remarks
14+
1315
A program database file (.pdb) was created using a newer version of mspdb*XXX*.dll than the one the compiler found on your system. This error usually indicates that mspdbsrv.exe or mspdbcore.dll are missing or have different versions than mspdb*XXX*.dll. (The *XXX* placeholder in the mspdb*XXX*.dll file name changes with each product release. For example, in Visual Studio 2015, the file name is mspdb140.dll.)
1416

1517
Ensure matching versions of mspdbsrv.exe, mspdbcore.dll, and mspdb*XXX*.dll are installed on your system. Ensure that mismatched versions have not been copied to the directory that contains the compiler and link tools for your target platform. For example, you might have copied the files so you could invoke the compiler or link tool from the command prompt without setting the **PATH** environment variable accordingly.

docs/error-messages/compiler-errors-1/fatal-error-c1903.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,4 +10,6 @@ ms.assetid: 4b4719d6-35d2-4ca5-81ce-903ecd28dfb9
1010

1111
> unable to recover from previous error(s); stopping compilation
1212
13+
## Remarks
14+
1315
The compiler found too many errors to continue. Fix the errors and recompile.

docs/error-messages/compiler-errors-1/fatal-error-c1904.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ ms.assetid: 10f66015-146f-41a7-8011-327b29dedec8
1010

1111
> bad provider interaction: 'file'
1212
13+
## Remarks
14+
1315
This error indicates the failure of an attribute provider.
1416

1517
Note the circumstances of the error, try to isolate the problem and create a reproducible test case, then contact [Talk to Us](/visualstudio/ide/talk-to-us).

docs/error-messages/compiler-errors-1/fatal-error-c1905.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ ms.assetid: fefc6769-477f-45a2-9878-6f0a5f42472c
1010

1111
> Front end and back end not compatible (must target same processor)
1212
13+
## Remarks
14+
1315
This error occurs when a .obj file is generated by a compiler front end (C1.dll) that targets one processor, such as x86, ARM, or x64, but is being read by a back end (C2.dll) that targets a different processor.
1416

1517
To fix this issue, ensure that you are using a matching front end and back end. This is the default for projects created in Visual Studio. This error may occur if you have edited the project file and used different paths to the compiler tools. If you have not specifically set the path for the compiler tools, then this error may occur if your Visual Studio installation is corrupt. For example, you may have copied the compiler .dll files from one location to another. Use **Programs and Features** in the Windows Control Panel to repair or reinstall Visual Studio.

0 commit comments

Comments
 (0)