Skip to content

Commit bd9c9bd

Browse files
Copilotadegeo
andcommitted
Fix errors from PR #49518: delete empty file, move TIP note, fix list numbering
Co-authored-by: adegeo <67293991+adegeo@users.noreply.github.com>
1 parent 06adc6d commit bd9c9bd

File tree

2 files changed

+11
-11
lines changed

2 files changed

+11
-11
lines changed

docs/visual-basic/reference/command-line-compiler/fix-vb-docs-command

Whitespace-only changes.

docs/visual-basic/reference/command-line-compiler/how-to-invoke-the-command-line-compiler.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -11,23 +11,23 @@ ms.assetid: 0fd9a8f6-f34e-4c35-a49d-9b9bbd8da4a9
1111
---
1212
# How to Invoke the Command-Line Compiler
1313

14+
You can invoke the command-line compiler by typing the name of its executable file into the command line, also known as the MS-DOS prompt. If you compile from the default Windows Command Prompt, you must type the fully qualified path to the executable file. To override this default behavior, you can either use the Developer Command Prompt for Visual Studio, or modify the PATH environment variable. Both allow you to compile from any directory by simply typing the compiler name.
15+
1416
[!TIP]
1517
For modern .NET projects, use the [`dotnet build`](../../../core/tools/dotnet-build.md) command to compile Visual Basic source files.
1618
The `vbc.exe` command-line compiler is only used for older .NET Framework projects.
1719

18-
You can invoke the command-line compiler by typing the name of its executable file into the command line, also known as the MS-DOS prompt. If you compile from the default Windows Command Prompt, you must type the fully qualified path to the executable file. To override this default behavior, you can either use the Developer Command Prompt for Visual Studio, or modify the PATH environment variable. Both allow you to compile from any directory by simply typing the compiler name.
19-
2020
[!INCLUDE[note_settings_general](~/includes/note-settings-general-md.md)]
2121

2222
## To invoke the compiler using the Developer Command Prompt for Visual Studio
2323

2424
1. Open the Visual Studio Tools program folder within the Microsoft Visual Studio program group.
2525

26-
2. You can use the **Developer Command Prompt for Visual Studio** to access the compiler from any directory on your machine, if Visual Studio is installed.
26+
1. You can use the **Developer Command Prompt for Visual Studio** to access the compiler from any directory on your machine, if Visual Studio is installed.
2727

28-
3. Open the **Developer Command Prompt for Visual Studio**.
28+
1. Open the **Developer Command Prompt for Visual Studio**.
2929

30-
4. At the command line, type `vbc.exe <sourceFileName>` and then press **Enter**.
30+
1. At the command line, type `vbc.exe <sourceFileName>` and then press **Enter**.
3131

3232
For example, if you stored your source code in a directory called `SourceFiles`, you would open the Command Prompt and type:
3333

@@ -42,23 +42,23 @@ vbc.exe Source.vb
4242

4343
The exact name of the directory where the compiler is located depends on the location of the Windows directory and the version of the ".NET Framework" installed. If you have more than one version of the ".NET Framework" installed, you must determine which version to use (typically the latest version).
4444

45-
2. From your **Start** Menu, right-click **My Computer**, and then click **Properties** from the shortcut menu.
45+
1. From your **Start** Menu, right-click **My Computer**, and then click **Properties** from the shortcut menu.
4646

47-
3. Click the **Advanced** tab, and then click **Environment Variables**.
47+
1. Click the **Advanced** tab, and then click **Environment Variables**.
4848

49-
4. In the **System** variables pane, select **Path** from the list and click **Edit**.
49+
1. In the **System** variables pane, select **Path** from the list and click **Edit**.
5050

51-
5. In the **Edit System** Variable dialog box, move the insertion point to the end of the string in the **Variable Value** field and type a semicolon (;) followed by the full directory name found in Step 1.
51+
1. In the **Edit System** Variable dialog box, move the insertion point to the end of the string in the **Variable Value** field and type a semicolon (;) followed by the full directory name found in Step 1.
5252

53-
6. Click **OK** to confirm your edits and close the dialog boxes.
53+
1. Click **OK** to confirm your edits and close the dialog boxes.
5454

5555
After you change the PATH environment variable, you can run the Visual Basic compiler at the Windows Command Prompt from any directory on the computer.
5656

5757
## To invoke the compiler using the Windows Command Prompt
5858

5959
1. From the **Start** menu, click on the **Accessories** folder, and then open the **Windows Command Prompt**.
6060

61-
2. At the command line, type `vbc.exe <sourceFileName>` and then press **Enter**.
61+
1. At the command line, type `vbc.exe <sourceFileName>` and then press **Enter**.
6262

6363
For example, if you stored your source code in a directory called `SourceFiles`, you would open the Command Prompt and type:
6464

0 commit comments

Comments
 (0)