You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ide/deploying-visual-cpp-application-by-using-the-vcpp-redistributable-package.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ You must have these components to complete this walkthrough:
54
54
55
55
- Your MFC application (.exe file).
56
56
57
-
- vcredist_x86.exe. This file is located in \Program Files (x86)\Microsoft Visual Studio \<version>\SDK\Bootstrapper\Packages\. You can also download this file from [Microsoft](https://www.microsoft.com/en-us/download/confirmation.aspx?id=5555).
57
+
- vcredist_x86.exe. This file is located in \Program Files (x86)\Microsoft Visual Studio \<version>\SDK\Bootstrapper\Packages\. You can also download this file from [Microsoft](https://www.microsoft.com/download/confirmation.aspx?id=5555).
58
58
59
59
- The setup.bat file that you created in the earlier step.
60
60
@@ -83,7 +83,7 @@ You must have these components to complete this walkthrough:
83
83
The self-extracting setup file installs the MFC application that is in the folder that you specified in step 2. The application runs successfully because the Visual C++ Redistributable Package installer is included in the self-extracting setup file.
84
84
85
85
> [!IMPORTANT]
86
-
> To determine which version of the runtime is installed, the installer checks the registry key \HKLM\SOFTWARE\Microsoft\VisualStudio\\<version>\VC\Runtimes\\<platform>. If the currently installed version is newer than the version that the installer is attempting to install, the installer returns success without installing the older version and leaves an additional entry on the installed programs page in the Control Panel.
86
+
> To determine which version of the runtime is installed, the installer checks the registry key \HKLM\SOFTWARE\Microsoft\VisualStudio\\\<version>\VC\Runtimes\\<platform>. If the currently installed version is newer than the version that the installer is attempting to install, the installer returns success without installing the older version and leaves an additional entry on the installed programs page in the Control Panel.
Copy file name to clipboardExpand all lines: docs/ide/walkthrough-compiling-a-cpp-program-that-targets-the-clr-in-visual-studio.md
+15-15Lines changed: 15 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -28,48 +28,48 @@ These topics assume that you understand the fundamentals of the C++ language.
28
28
1. From the Visual C++ project types, click **CLR**, and then click **CLR Empty Project**.
29
29
30
30
> [!NOTE]
31
-
> If the **CLR Empty Project** type is missing, select **Open Visual Studio Installer** in the left pane of the **New Project** dialog box. Install the option located under **Desktop development with C++** in the **Optional** components section, named **C++/CLI Support**.
31
+
> If the **CLR Empty Project** type is missing (Visual Studio 2017 only), select **Open Visual Studio Installer** in the left pane of the **New Project** dialog box. Install the option located under **Desktop development with C++** in the **Optional** components section, named **C++/CLI Support**.<br/>
32
32
33
33
1. Type a project name.
34
34
35
-
By default, the solution that contains the project has the same name as the new project, but you can enter a different name. You can enter a different location for the project if you want.
35
+
By default, the solution that contains the project has the same name as the new project, but you can enter a different name. You can enter a different location for the project if you want.
36
36
37
-
Click **OK** to create the new project.
37
+
Click **OK** to create the new project.
38
38
39
39
1. If **Solution Explorer** is not visible, click **Solution Explorer** on the **View** menu.
40
40
41
41
1. Add a new source file to the project:
42
42
43
-
- Right-click the **Source Files** folder in **Solution Explorer**, point to **Add** and click **New Item**.
43
+
- Right-click the **Source Files** folder in **Solution Explorer**, point to **Add** and click **New Item**.
44
44
45
-
- Click **C++ File (.cpp)** and type a file name and then click **Add**.
45
+
- Click **C++ File (.cpp)** and type a file name and then click **Add**.
46
46
47
-
The **.cpp** file appears in the **Source Files** folder in **Solution Explorer** and a tabbed window appears where you type the code you want in that file.
47
+
The **.cpp** file appears in the **Source Files** folder in **Solution Explorer** and a tabbed window appears where you type the code you want in that file.
48
48
49
49
1. Click in the newly created tab in Visual Studio and type a valid Visual C++ program, or copy and paste one of the sample programs.
50
50
51
-
For example, you can use the [How to: Write a Text File (C++/CLI)](../dotnet/how-to-write-a-text-file-cpp-cli.md) sample program (in the **File Handling and I/O** node of the Programming Guide).
51
+
For example, you can use the [How to: Write a Text File (C++/CLI)](../dotnet/how-to-write-a-text-file-cpp-cli.md) sample program (in the **File Handling and I/O** node of the Programming Guide).
52
52
53
-
If you use the sample program, notice that you use the `gcnew` keyword instead of `new` when creating a .NET object, and that `gcnew` returns a handle (`^`) rather than a pointer (`*`):
53
+
If you use the sample program, notice that you use the `gcnew` keyword instead of `new` when creating a .NET object, and that `gcnew` returns a handle (`^`) rather than a pointer (`*`):
For more information on the new Visual C++ syntax, see [Component Extensions for Runtime Platforms](../windows/component-extensions-for-runtime-platforms.md).
57
+
For more information on the new Visual C++ syntax, see [Component Extensions for Runtime Platforms](../windows/component-extensions-for-runtime-platforms.md).
58
58
59
59
1. On the **Build** menu, click **Build Solution**.
60
60
61
-
The **Output** window displays information about the compilation progress, such as the location of the build log and a message that indicates the build status.
61
+
The **Output** window displays information about the compilation progress, such as the location of the build log and a message that indicates the build status.
62
62
63
-
If you make changes and run the program without doing a build, a dialog box might indicate that the project is out of date. Select the checkbox on this dialog before you click **OK** if you want Visual Studio to always use the current versions of files instead of prompting you each time it builds the application.
63
+
If you make changes and run the program without doing a build, a dialog box might indicate that the project is out of date. Select the checkbox on this dialog before you click **OK** if you want Visual Studio to always use the current versions of files instead of prompting you each time it builds the application.
64
64
65
65
1. On the **Debug** menu, click **Start without Debugging**.
66
66
67
67
1. If you used the sample program, when you run the program a command window is displayed that indicates the text file has been created.
68
68
69
-
The **textfile.txt** text file is now located in your project directory. You can open this file by using Notepad.
69
+
The **textfile.txt** text file is now located in your project directory. You can open this file by using Notepad.
70
70
71
-
> [!NOTE]
72
-
> Choosing the empty CLR project template automatically set the `/clr` compiler option. To verify this, right-click the project in **Solution Explorer** and clicking **Properties**, and then check the **Common Language Runtime support** option in the **General** node of **Configuration Properties**.
71
+
> [!NOTE]
72
+
> Choosing the empty CLR project template automatically set the `/clr` compiler option. To verify this, right-click the project in **Solution Explorer** and clicking **Properties**, and then check the **Common Language Runtime support** option in the **General** node of **Configuration Properties**.
0 commit comments