6 Apr
2017
6 Apr
'17
2:41 p.m.
On Thu, Apr 6, 2017 at 9:32 AM, Peter Dimov via Boost <boost@lists.boost.org
wrote:
Tom Kent wrote:
That doesn't help us for the installs of VS2017 that are already out there
and may not see updates. We definitely can't depend on users getting the VS update in a timely manner.
We could first try the usual install locations, then if no installation is found there, try to use vswhere.exe, and if that also fails, well, there's always the fallback of using the 2017 command prompt. This would cover 99.4% of the users.
That's roughly the longer term plan. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail