Merge pull request #4396 from Michael-Eng/patch-1

Deprecate VCTargets

Author: PRMerger17

docs/extensibility/set-install-root.md

@@ -9,19 +9,20 @@ manager: jillfra
 ms.workload:
   - "vssdk"
 ---
-# Installing outside the extensions folder
+# Install outside the extensions folder
 
-Starting with Visual Studio 2017 and VSIX v3 (version 3), there is now support for installing extension assets outside of the extensions folder. Currently, the following locations are enabled as valid installation locations (where [INSTALLDIR] is mapped to the Visual Studio instance's installation directory):
+Starting with Visual Studio 2017 and VSIX v3 (version 3), extension assets can be installed outside of the extensions folder. Currently, the following locations are enabled as valid installation locations (where [INSTALLDIR] is mapped to the Visual Studio instance's installation directory):
 
 * [INSTALLDIR]\MSBuild
 * [INSTALLDIR]\Xml\Schemas
 * [INSTALLDIR]\Common7\IDE\PublicAssemblies
 * [INSTALLDIR]\Licenses
 * [INSTALLDIR]\Common7\IDE\ReferenceAssemblies
 * [INSTALLDIR]\Common7\IDE\RemoteDebugger
-* [INSTALLDIR]\Common7\IDE\VC\VCTargets
+* [INSTALLDIR]\Common7\IDE\VC\VCTargets (only supported for Visual Studio 2017; deprecated for Visual Studio 2019 and later)
 
->**Note:** The VSIX format does not allow you to install outside the VS install folder structure.
+> [!NOTE]
+> The VSIX format doesn't allow you to install outside the Visual Studio install folder structure. 
 
 In order to support installing to these directories, the VSIX must be installed "per-instance per-machine". This can be enabled by checking the "all-users" checkbox in the extension.vsixmanifest designer:
 
@@ -43,7 +44,8 @@ This will add some metadata to the corresponding `ProjectReference` property ins
  </ProjectReference>
 ```
 
->**Note:** You can edit the .csproj file directly, if you prefer.
+> [!NOTE]
+> You can edit the .csproj file directly, if you prefer.
 
 ## How to set a subpath under the InstallRoot