Skip to content
This repository has been archived by the owner on Sep 11, 2021. It is now read-only.

vs_BuildTools 2019 #224

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from
Draft

vs_BuildTools 2019 #224

wants to merge 5 commits into from

Conversation

aminya
Copy link

@aminya aminya commented Aug 25, 2020

Closes #194

@aminya aminya force-pushed the vs2019 branch 2 times, most recently from 9a7484b to 00e2148 Compare August 25, 2020 09:20
@aminya
Copy link
Author

aminya commented Aug 25, 2020

Where can I find the installation log for vs2019?
@jacobq

@jacobq jacobq mentioned this pull request Aug 25, 2020
@jacobq
Copy link
Collaborator

jacobq commented Jan 23, 2021

Where can I find the installation log for vs2019?
@jacobq

Sorry for not responding sooner! This got buried in my list of notifications and forgotten long ago. Unfortunately, I actually do not know where the VS installer produces log files (apart from the usual suspects of stdout and stderr). Taking a quick peek at Use command-line parameters to install Visual Studio, Install Build Tools into a container, and Visual Studio Build Tools component directory may help you get some clues though. e.g. the first of those mentions:

Each operation generates several log files in the %TEMP% directory that indicate the progress of the installation. Sort the folder by date and look for files that begin with dd_bootstrapper, dd_client, and dd_setup for the bootstrapper, the installer app, and the setup engine, respectively.

Not sure why, but it looks like we have a log file option when installing VS2015 but not when installing VS2017. Looks like that gets used here:

logPath: BUILD_TOOLS.logName ? path.join(directory, BUILD_TOOLS.logName) : null,

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support Visual Studio 2019
2 participants