Merge pull request #11866 from Mikejo5000/mikejo-br21

Consolidate two articles on configuring VSTO

Author: JamesJBarnett

.openpublishing.redirection.json

@@ -1875,6 +1875,11 @@
       "redirect_url": "/troubleshoot/developer/visualstudio/project-build/troubleshoot-resource-editor-errors",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/vsto/configuring-a-computer-to-develop-office-solutions.md",
+      "redirect_url": "/visualstudio/vsto/how-to-configure-a-computer-to-develop-office-solutions",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/vsto/troubleshooting-office-solution-deployment.md",
       "redirect_url": "/troubleshoot/developer/visualstudio/tools-utilities/troubleshooting-office-solution-deployment",

docs/vsto/configuring-a-computer-to-develop-office-solutions.md

@@ -33,7 +33,7 @@ ms.technology: office-development
   Not all applications can use every project type. For example, document-level projects are available only for Microsoft Office Word and Microsoft Office Excel. Similarly, some features are available only for certain types of projects or applications. For example, the actions pane is available only in document-level projects, and Ribbon extensions are available only for some applications. For more information about the different project types, see [Office solutions development overview (VSTO)](../vsto/office-solutions-development-overview-vsto.md).
 
 > [!NOTE]
-> Office project templates are available only in some editions of Visual Studio. For more information, see [Configure a computer to develop Office solutions](../vsto/configuring-a-computer-to-develop-office-solutions.md).
+> Office project templates are available only in some editions of Visual Studio. For more information, see [Configure a computer to develop Office solutions](../vsto/how-to-configure-a-computer-to-develop-office-solutions.md).
 
 ## Project types available for different Microsoft Office applications
  The following table shows the applications that you can use with each project type.

docs/vsto/features-available-by-office-application-and-project-type.md

@@ -34,7 +34,7 @@ ms.technology: office-development
 
  Describes which applications and projects are required to use Office development features such as Ribbon extensibility, custom task panes, actions panes, and form regions.
 
-- [Configure a computer to develop Office solutions](../vsto/configuring-a-computer-to-develop-office-solutions.md)
+- [Configure a computer to develop Office solutions](../vsto/how-to-configure-a-computer-to-develop-office-solutions.md)
 
  Provides information and steps for installing the Office development tools, the runtime that enables Office solutions to run on end-user computers, and the Office primary interop assemblies.
 

docs/vsto/getting-started-office-development-in-visual-studio.md

@@ -18,20 +18,48 @@ ms.technology: office-development
 # Configure a computer to develop Office solutions
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
-  To configure a development computer so that you can use the Microsoft Office developer tools in Visual Studio, follow the instructions in this topic. You must have administrative privileges on the development computer to perform these steps.
 
-### To configure the development computer
+To configure a development computer so that you can use the Microsoft Office developer tools in Visual Studio, follow the instructions in this topic. You must have administrative privileges on the development computer to perform these steps.
 
-1. Install a version of Visual Studio that includes the Office developer tools. The Office developer tools are installed by default. If you customize the Visual Studio installation by selecting which features to install, make sure that **Microsoft Office Developer Tools** is selected during setup. For more information about the versions of Visual Studio that include the Office developer tools, see [Configure a computer to develop Office solutions](../vsto/configuring-a-computer-to-develop-office-solutions.md).
+## Requirements
 
-2. Install a version of Office that is supported by the Office developer tools in Visual Studio. For more information, see [Configure a computer to develop Office solutions](../vsto/configuring-a-computer-to-develop-office-solutions.md).
+The following versions of Visual Studio, the .NET Framework, and Microsoft Office are supported.
 
-     Make sure that you also install the PIAs for the version of Office that you install. The PIAs are installed with Office by default. If you modify Office setup, make sure that the **.NET Programmability Support** feature is selected for the applications you want to target.
+|Software|Supported versions|
+|--------------|------------------------|
+|Visual Studio 2017| Any edition with the **Office/SharePoint development** workload.|
+|.NET Framework|- The .NET Framework 4 or later.|
+|Microsoft Office|<ul><li>Any suite edition of Office including Microsoft 365 apps for enterprise.</li><li>Any of the following standalone applications:<br /><br /> <ul><li>Excel</li><li>InfoPath (Office 2013 and Office 2010 only)</li><li>Outlook</li><li>PowerPoint</li><li>Project</li><li>Visio</li><li>Word</li></ul></li></ul><br /> Visual Basic for Applications (VBA) must be installed as part of Office. **Important:** Click-to-Run versions of Office 2010 applications are not supported.|
 
-3. If you have an English version of Visual Studio but use non-English settings for Windows, you can install the  Visual Studio Tools for Office runtime  language pack to see  Visual Studio Tools for Office runtime  messages in the same language as Windows. Non-English versions of Visual Studio automatically install the language pack.
+## Configure the development computer
+
+1. Install a version of Visual Studio that includes the Office developer tools. The Office developer tools are installed by default. If you customize the Visual Studio installation by selecting which features to install, make sure that **Microsoft Office Developer Tools** is selected during setup.
+
+2. Install a version of Office that is supported by the Office developer tools in Visual Studio.
+
+   Make sure that you also install the PIAs for the version of Office that you install. The PIAs are installed with Office by default. If you modify Office setup, make sure that the **.NET Programmability Support** feature is selected for the applications you want to target.
+
+3. If you have an English version of Visual Studio but use non-English settings for Windows, you can install the [Visual Studio Tools for Office runtime language pack](https://www.microsoft.com/en-us/download/details.aspx?id=105672) to see Visual Studio Tools for Office runtime messages in the same language as Windows. Non-English versions of Visual Studio automatically install the language pack. The language pack is available from the [Microsoft download center](https://www.microsoft.com/en-us/download/).
+
+## If project templates don't appear or they don't work in Visual Studio
+
+If you install a supported version of Visual Studio, the .NET Framework, and Microsoft Office, but Office project templates either don't appear in the Visual Studio **New Project** dialog box, or you receive an error when you try to use one, check the following:
+
+- Ensure that you have the Microsoft Office developer tools installed on your computer.
+
+     Office developer tools are an optional component of Visual Studio, but they are installed automatically along with Visual Studio. If you customize the Visual Studio installation by specifying which features to install, make sure that you choose **Microsoft Office Developer Tools** during setup to install the tools.
+
+     To make sure that these tools are installed, start the Visual Studio setup program, and choose the **Modify** button. Select the **Microsoft Office Developer Tools** check box, and then choose the **Update** button.
+
+- Make sure that you're not running a version of Office that was delivered by Click-to-Run. See [How to: Verify whether Outlook is a Click-to-Run application on a computer](/previous-versions/office/developer/office-2010/ff864733(v=office.14)).
+
+- Ensure that you're running only one version of Microsoft Office.
+
+If you continue to experience problems, see [Additional support for errors in Office solutions](../vsto/additional-support-for-errors-in-office-solutions.md).
 
 ## See also
 
 - [Get started &#40;Office development in Visual Studio&#41;](../vsto/getting-started-office-development-in-visual-studio.md)
 - [How to: Install the Visual Studio Tools for Office runtime redistributable](../vsto/how-to-install-the-visual-studio-tools-for-office-runtime-redistributable.md)
 - [How to: Install Office primary interop assemblies](../vsto/how-to-install-office-primary-interop-assemblies.md)
+- [Features available by Office application and project type](../vsto/features-available-by-office-application-and-project-type.md)

docs/vsto/how-to-configure-a-computer-to-develop-office-solutions.md

@@ -51,8 +51,7 @@ ms.technology: office-development
 ## See also
 
 - [Get started (Office development in Visual Studio)](../vsto/getting-started-office-development-in-visual-studio.md)
-- [Configure a computer to develop Office solutions](../vsto/configuring-a-computer-to-develop-office-solutions.md)
-- [How to: Configure a computer to develop Office solutions](../vsto/how-to-configure-a-computer-to-develop-office-solutions.md)
+- [Configure a computer to develop Office solutions](../vsto/how-to-configure-a-computer-to-develop-office-solutions.md)
 - [How to: Install Office primary interop assemblies](../vsto/how-to-install-office-primary-interop-assemblies.md)
 - [Manage documents on a server by using the ServerDocument class](../vsto/managing-documents-on-a-server-by-using-the-serverdocument-class.md)
 - [Deploy an Office solution](../vsto/deploying-an-office-solution.md)

docs/vsto/how-to-install-the-visual-studio-tools-for-office-runtime-redistributable.md

@@ -1 +1 @@
-  An edition of Visual Studio that includes the Microsoft Office developer tools. For more information, see [Configure a computer to develop Office solutions](../../vsto/configuring-a-computer-to-develop-office-solutions.md).
+  An edition of Visual Studio that includes the Microsoft Office developer tools. For more information, see [Configure a computer to develop Office solutions](../../vsto/how-to-configure-a-computer-to-develop-office-solutions.md).

docs/vsto/includes/vsto-vsprereq-md.md

@@ -16,12 +16,13 @@ ms.technology: office-development
 # Microsoft Office is not installed on the computer
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
-  Visual Studio cannot find the Microsoft Office application that corresponds to the project type. If you are developing a VSTO Add-in project, it means that you cannot debug or run the project. If you are trying to create a document-level project, this means that you cannot create the project.
+  Visual Studio can't find the Microsoft Office application that corresponds to the project type. If you're developing a VSTO Add-in project, it means that you can't debug or run the project. If you're trying to create a document-level project, this message means that you can't create the project.
 
 ## To correct the error
 
-1. Install the Microsoft Office application associated with the project type, including the primary interop assemblies. For more information about supported versions of Microsoft Office, see [Configure a computer to develop Office solutions](../vsto/configuring-a-computer-to-develop-office-solutions.md).
+1. Install the Microsoft Office application associated with the project type, including the primary interop assemblies. For more information about supported versions of Microsoft Office, see [Configure a computer to develop Office solutions](../vsto/how-to-configure-a-computer-to-develop-office-solutions.md).
 
 ## See also
+
 - [Configure a computer to develop Office solutions](../vsto/configuring-a-computer-to-develop-office-solutions.md)
 - [How to: Configure a computer to develop Office solutions](../vsto/how-to-configure-a-computer-to-develop-office-solutions.md)

docs/vsto/microsoft-office-is-not-installed-on-this-computer.md

@@ -67,7 +67,7 @@ For Visual Studio 2017 and later, these copies of the PIAs are installed to foll
 
 ### Primary interop assemblies in the global assembly cache
 
-To perform certain development tasks, the PIAs must be installed and registered in the global assembly cache on the development computer. Typically, the PIAs are installed automatically when you install Office on the development computer. For more information, see [Configure a computer to develop Office solutions](../vsto/configuring-a-computer-to-develop-office-solutions.md).
+To perform certain development tasks, the PIAs must be installed and registered in the global assembly cache on the development computer. Typically, the PIAs are installed automatically when you install Office on the development computer. For more information, see [Configure a computer to develop Office solutions](../vsto/how-to-configure-a-computer-to-develop-office-solutions.md).
 
 The Office PIAs aren't required on end-user computers to run Office solutions. For more information, see [Design and create Office solutions](../vsto/designing-and-creating-office-solutions.md).
 
@@ -88,7 +88,7 @@ If you've installed and registered the PIAs in the global assembly cache, these
 
 ## Primary interop assemblies for Microsoft Office applications
 
-The following table lists the primary interop assemblies that are available for  Office 2016 ,  Office 2013  and Office 2010.
+The following table lists the primary interop assemblies that are available for  Office 2016, Office 2013, and Office 2010.
 
 <br/>
 
@@ -108,7 +108,7 @@ The following table lists the primary interop assemblies that are available for
 |Microsoft Publisher 14.0 Object Library<br /><br /> Microsoft Publisher 15.0 Object Library|Microsoft.Office.Interop.Publisher.dll|
 |Microsoft SharePoint Designer 14.0 Web Object Reference Library|Microsoft.Office.Interop.SharePointDesigner.dll|
 |Microsoft SharePoint Designer 14.0 Page Object Reference Library|Microsoft.Office.Interop.SharePointDesignerPage.dll|
-|Microsoft Smart Tags 2.0 Type Library **Note:**  Smart tags are deprecated in  Excel 2010  and  Word 2010 .|Microsoft.Office.Interop.SmartTag.dll|
+|Microsoft Smart Tags 2.0 Type Library **Note:**  Smart tags are deprecated in  Excel 2010 and Word 2010.|Microsoft.Office.Interop.SmartTag.dll|
 |Microsoft Visio 14.0 Type Library<br /><br /> Microsoft Visio 15.0 Type Library|Microsoft.Office.Interop.Visio.dll|
 |Microsoft Visio 14.0 Save As Web Type Library<br /><br /> Microsoft Visio 15.0 Save As Web Type Library|Microsoft.Office.Interop.Visio.SaveAsWeb.dll|
 |Microsoft Visio 14.0 Drawing Control Type Library<br /><br /> Microsoft Visio 15.0 Drawing Control Type Library|Microsoft.Office.Interop.VisOcx.dll|
@@ -119,7 +119,7 @@ The following table lists the primary interop assemblies that are available for
 
 When you install and register the Office PIAs in the global assembly cache (either with Office or by installing the redistributable package for the PIAs), the binding redirect assemblies are also installed only in the global assembly cache. These assemblies ensure that the correct version of the primary interop assemblies is loaded at run time.
 
-For example, when a solution that references a Office 2010 assembly runs on a computer that has the  Office 2013  version of the same primary interop assembly, the binding redirect assembly instructs the .NET Framework runtime to load the  Office 2013  version of the primary interop assembly.
+For example, when a solution that references an Office 2010 assembly runs on a computer that has the  Office 2013  version of the same primary interop assembly, the binding redirect assembly instructs the .NET Framework runtime to load the  Office 2013  version of the primary interop assembly.
 
 For more information, see [How to: Enable and disable automatic binding redirection](/dotnet/framework/configure-apps/how-to-enable-and-disable-automatic-binding-redirection).