visual studio 2015 update

Author: mtx48109

docs/windows/walkthrough-creating-a-standard-cpp-program-cpp.md

@@ -31,14 +31,20 @@ To complete this walkthrough, you must understand the fundamentals of the C++ la
 
 1. Create a project by pointing to **New** on the **File** menu, and then clicking **Project**.
 
-1. In the **Visual C++** project types pane, click **Windows Desktop**, and then click **Windows Console Application**.
+1. In the **Visual C++** project types pane, click **Windows Desktop**, and then click **Windows Console Application**. 
 
-1. Type a name for the project.
+   > [!NOTE]
+   > For versions of Visual Studio older than 2017, in the **New Project** dialog box, expand **Installed** > **Templates** > **Visual C++**, and then select **Win32**. In the center pane, select **Win32 Console Application**. 
+
+   Type a name for the project.
 
    By default, the solution that contains the project has the same name as the project, but you can type a different name. You can also type a different location for the project.
 
    Click **OK** to create the project.
 
+   > [!NOTE]
+   > For versions of Visual Studio older than 2017, complete the **Win32 Application Wizard**. Click **Next**, then make sure **Console Application** is selected and uncheck the **Precompiled Headers** box. Click **Finish**.
+
 1. If **Solution Explorer** is not displayed, on the **View** menu, click **Solution Explorer**.
 
 1. Add a new source file to the project, as follows.

docs/windows/walkthrough-creating-and-using-a-static-library-cpp.md

@@ -37,17 +37,26 @@ An understanding of the fundamentals of the C++ language.
 
 1. On the menu bar, choose **File** > **New** > **Project**.
 
-1. In the left pane of the **New Project** dialog box, expand **Installed** > **Visual C++**, and then select **Windows Desktop**.
+1. In the left pane of the **New Project** dialog box, expand **Installed** > **Visual C++**, and then select **Windows Desktop**. In the center pane, select **Windows Desktop Wizard**.
 
-1. In the center pane, select **Windows Desktop Wizard**.
+   > [!NOTE]
+   > For versions of Visual Studio older than 2017, in the **New Project** dialog box, expand **Installed** > **Templates** > **Visual C++**, and then select **Win32**. In the center pane, select **Win32 Console Application**.
 
 1. Specify a name for the project—for example, *MathFuncsLib*—in the **Name** box. Specify a name for the solution—for example, *StaticLibrary*—in the **Solution Name** box. Choose the **OK** button.
 
-1. Under **Application type**, select Static Library (.lib).
+    - For Visual Studio 2017,
+
+        1. Under **Application type**, select **Static Library (.lib)**.
+
+        1. Under **Additioal Options**, un-check the **Precompiled header** check box.
+
+        1. Choose **OK** to create the project.
+
+    - For versions of Visual Studio older than 2017,
 
-1. Under **Additional Options**, un-check the **Precompiled header** check box.
+        1. Click **Next**.
 
-1. Choose **OK** to create the project.
+        1. Under **Application type**, select **Static library**. Then uncheck the **Precompiled header** box and choose **Finish**.
 
 ##  <a name="AddClassToLib"></a> Adding a class to the static library
 
@@ -76,17 +85,26 @@ An understanding of the fundamentals of the C++ language.
 
 1. On the menu bar, choose **File** > **New** > **Project**.
 
-1. In the left pane of the **New Project** dialog box, expand **Installed** > **Visual C++**, and then select **Windows Desktop**.
+1. In the left pane of the **New Project** dialog box, expand **Installed** > **Visual C++**, and then select **Windows Desktop**. In the center pane, select **Windows Desktop Wizard**. 
 
-1. In the center pane, select **Windows Desktop Wizard**.
+   > [!NOTE]
+   > For versions of Visual Studio older than 2017, in the **New Project** dialog box, expand **Installed** > **Templates** > **Visual C++**, and then select **Win32**. In the center pane, select **Win32 Console Application**.
 
 1. Specify a name for the project—for example, *MyExecRefsLib*—in the **Name** box. In the drop-down list next to **Solution**, select **Add to Solution**. This adds the new project to the solution that contains the static library. Choose the **OK** button.
 
-1. Under **Application type**, select **Console Application (.exe)**.
+    - For Visual Studio 2017,
+
+        1. Under **Application type**, select **Console Application (.exe)**.
+
+        1. Under **Additioal Options**, un-check the **Precompiled header** check box.
+
+        1. Choose **OK** to create the project.
+
+    - For versions of Visual Studio older than 2017,
 
-1. Under **Additioal Options**, un-check the **Precompiled header** check box.
+        1. Click **Next**.
 
-1. Choose **OK** to create the project.
+        1. Make sure **Console application** is selected. Then check the **Empty Project** box and choose **Finish**.
 
 ##  <a name="UseLibInApp"></a> Using the functionality from the static library in the app
 

docs/windows/walkthrough-creating-windows-desktop-applications-cpp.md

@@ -107,7 +107,7 @@ Next, you'll learn how to create the code for a Windows desktop application in V
    For information about the parameters and return value of this function, see [WinMain entry point](https://msdn.microsoft.com/library/windows/desktop/ms633559).
 
    > [!NOTE]
-   > What are all those extra words, such as `CALLBACK`, or `HINSTANCE`, or `_In_`? The traditional Windows API uses typedefs and preprocessor macros extensively to abstract away some of the details of types and platform-specific code, such as calling conventions, **__declspec** declarations, and compiler pragmas. In Visual Studio, you can use the IntelliSense [Quick Info](/visualstudio/ide/using-intellisense#quick-info) feature to see what these typedefs and macros define. Hover your mouse over the word of interest, or select it and press ctrl-K, ctrl-I for a small pop-up window that contains the definition. For more information, see [Using IntelliSense](/visualstudio/ide/using-intellisense). Parameters and return types often use *SAL Annotations* to help you catch programming errors. For more information, see [Using SAL Annotations to Reduce C/C++ Code Defects](/visualstudio/code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects).
+   > What are all those extra words, such as `CALLBACK`, or `HINSTANCE`, or `_In_`? The traditional Windows API uses typedefs and preprocessor macros extensively to abstract away some of the details of types and platform-specific code, such as calling conventions, **__declspec** declarations, and compiler pragmas. In Visual Studio, you can use the IntelliSense [Quick Info](/visualstudio/ide/using-intellisense#quick-info) feature to see what these typedefs and macros define. Hover your mouse over the word of interest, or select it and press **Ctrl**+**K**, **Ctrl**+**I** for a small pop-up window that contains the definition. For more information, see [Using IntelliSense](/visualstudio/ide/using-intellisense). Parameters and return types often use *SAL Annotations* to help you catch programming errors. For more information, see [Using SAL Annotations to Reduce C/C++ Code Defects](/visualstudio/code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects).
 
 1. Windows desktop programs require <windows.h>. <tchar.h> defines the `TCHAR` macro, which resolves ultimately to **wchar_t** if the UNICODE symbol is defined in your project, otherwise it resolves to **char**.  If you always build with UNICODE enabled, you don't need TCHAR and can just use **wchar_t** directly.