Merge branch 'master' into pchapman-working

Author: PoulChapman

docs/extensibility/media/install-root-properties.png

@@ -33,13 +33,13 @@ translation.priority.mt:
 
 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):
 
-* [INSTALLDIR]\Common7\IDE\PublicAssemblies
-* [INSTALLDIR]\Common7\IDE\ReferenceAssemblies
 * [INSTALLDIR]\MSBuild
-* [INSTALLDIR]\Schemas
+* [INSTALLDIR]\Xml\Schemas
+* [INSTALLDIR]\Common7\IDE\PublicAssemblies
 * [INSTALLDIR]\Licenses
-* [INSTALLDIR]\RemoteDebugger
-* [INSTALLDIR]\VSTargets
+* [INSTALLDIR]\Common7\IDE\ReferenceAssemblies
+* [INSTALLDIR]\Common7\IDE\RemoteDebugger
+* [INSTALLDIR]\Common7\IDE\VC\VCTargets
 
 >**Note:** The VSIX format does not allow you to install outside the VS install folder structure.
 

docs/extensibility/media/set-subpath.png

@@ -1,8 +1,8 @@
 ---
 title: "Install on low bandwidth or unreliable network environments | Microsoft Docs"
 description: "Describes how the Visual Studio installer works in unreliable network conditions, and explains how to download install files before beginning the installation."
-ms.date: "04/14/2017"
-ms.reviewer: ""
+ms.date: "08/25/2017"
+ms.reviewer: "tims"
 ms.suite: ""
 ms.technology:
  - "vs-ide-install"
@@ -15,29 +15,15 @@ ms.assetid: 44DB1998-68CD-4560-870A-EE5B993DCF6E
 author: "timsneath"
 ms.author: "tims"
 manager: "ghogen"
-translation.priority.ht:
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "ru-ru"
-  - "zh-cn"  
-  - "zh-tw"
-translation.priority.mt:
-  - "cs-cz"
-  - "pl-pl"
-  - "pt-br"
-  - "tr-tr"
 ---
 
 # Install Visual Studio 2017 on low bandwidth or unreliable network environments
 We designed the new Visual Studio 2017 installer to work well in a wide variety of network and machine conditions.
 
 - The files you'll need to install Visual Studio are distributed on a global delivery network, so we can get them to you from a local server;
 - During the installation process, we try three different download technologies (WebClient, BITS and WinInet) to minimize interference with anti-virus and proxy software;
-- The new workload-based model means you'll need to install less than with previous versions of Visual Studio.
+- Compared to a generic "ISO" or zip file, we download only the packages you need for your machine, for example, we don't download 64-bit files if you don't need them;
+- The new workload-based model means you'll need to download far less than with previous versions of Visual Studio: as little as 300MB for the smallest installation.
 
 We therefore recommend that you give the new web installer a try - we think you'll find it a good experience. But if you want to be sure that you've downloaded the installation files successfully before you start installing Visual Studio, we've got you covered. You can use the command line to create a local cache of the files you need before starting the install.
 
@@ -55,39 +41,40 @@ Your setup file—or to be more specific, a bootstrapper file—will mat
 | Visual Studio Enterprise   | [vs_enterprise.exe](https://aka.ms/vs/15/release/vs_enterprise.exe)     |
 
 ## Create a local install cache
-To create a local layout, open a command prompt and use one of the commands from the following examples. The examples here assume that you've downloaded the Visual Studio Community bootstrapper: adjust the command as appropriate for your edition.
+To create a local layout, open a command prompt and use one of the commands from the following examples. The examples here assume that you're using the Community edition of Visual Studio; adjust the command as appropriate for your edition.
 
 - For .NET web and .NET desktop development, run:
-  ```
-  vs_community.exe --layout c:\vs2017layout --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.VisualStudio.Workload.NetWeb --add Component.GitHub.VisualStudio --includeOptional --lang en-US
-  ```
+```
+vs_community.exe --layout c:\vs2017layout --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.VisualStudio.Workload.NetWeb --add Component.GitHub.VisualStudio --includeOptional --lang en-US
+```
+
 - For .NET desktop and Office development, run:
-  ```
-  vs_community.exe --layout c:\vs2017layout --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.VisualStudio.Workload.Office --includeOptional --lang en-US
-  ```
+```
+vs_community.exe --layout c:\vs2017layout --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.VisualStudio.Workload.Office --includeOptional --lang en-US
+```
+
 - For C++ desktop development, run:
-  ```
-  vs_community.exe --layout c:\vs2017layout --add Microsoft.VisualStudio.Workload.NativeDesktop --includeRecommended --lang en-US
-  ```
+```
+vs_community.exe --layout c:\vs2017layout --add Microsoft.VisualStudio.Workload.NativeDesktop --includeRecommended --lang en-US
+```
 
 - To create a complete local layout with all features (this will take a long time - we have _lots_ of features!), run:
-  ```
-  vs_community.exe --layout c:\vs2017layout --lang en-US
-  ```
+```
+vs_community.exe --layout c:\vs2017layout --lang en-US
+```
 
 If you want to install a language other than English, change `en-US` to a locale from the list at the bottom of this page. Use this [list of the components and workloads available](workload-and-component-ids.md) to further customize your installation cache as necessary.
 
 ## Install from the local cache
-When you run from a local install cache, we'll use the local versions of each of these files. But if you select components during installation that aren't in the cache, we'll attempt to download them from the internet.
+> [!TIP]
+> When you run from a local install cache, we'll use the local versions of each of these files. But if you select components during installation that aren't in the cache, we'll attempt to download them from the internet.
 
 To ensure that you only install the files you've downloaded, use the same command-line options that you used to create the layout cache. For example, if you created a layout cache with the following command:
-
 ```
 vs_community.exe --layout c:\vs2017layout --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.VisualStudio.Workload.NetWeb --add Component.GitHub.VisualStudio --includeOptional --lang en-US
 ```
 
 use this command to run the installation:
-
 ```
 c:\vs2017layout\vs_community.exe --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.VisualStudio.Workload.NetWeb --add Component.GitHub.VisualStudio --includeOptional
 ```