K
Kenneth Porter
Guest
I'm trying to create a network install layout to install the native compiler on more than one machine, and to avoid re-downloading to re-install.
I downloaded the pre-release community bootstrapper for 2019 on March 4. I run it to create a layout for the native C++ tools. I then launch vs_setup.exe from the resulting (local) directory and it wants to download an additional 1.2 GB of content. Why wasn't this downloaded during the initial vs_community.exe run? I do see the NativeDesktop listed in Catalog.json. Here's my layout command:
.\vs_community.exe --layout f:\tmp\VisualStudio\vs2019 --lang en-US --add Microsoft.VisualStudio.Workload.NativeDesktop
F: is a local drive.
Based on this list, I'm expecting to see a Microsoft.VisualStudio.Component.VC.Tools.x86.x64 directory in the layout, but it's not there.
Visual Studio Community workload and component IDs
Continue reading...
I downloaded the pre-release community bootstrapper for 2019 on March 4. I run it to create a layout for the native C++ tools. I then launch vs_setup.exe from the resulting (local) directory and it wants to download an additional 1.2 GB of content. Why wasn't this downloaded during the initial vs_community.exe run? I do see the NativeDesktop listed in Catalog.json. Here's my layout command:
.\vs_community.exe --layout f:\tmp\VisualStudio\vs2019 --lang en-US --add Microsoft.VisualStudio.Workload.NativeDesktop
F: is a local drive.
Based on this list, I'm expecting to see a Microsoft.VisualStudio.Component.VC.Tools.x86.x64 directory in the layout, but it's not there.
Visual Studio Community workload and component IDs
Continue reading...