Re: [boost] [VS2017][release] vswhere.exe

Subject: Re: [boost] [VS2017][release] vswhere.exe
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2017-04-06 14:40:19

On 04/06/17 16:54, Paul A. Bristow via Boost wrote:
>
>> -----Original Message-----
>> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of degski via Boost
>> Sent: 06 April 2017 14:19
>> To: boost
>> Cc: degski
>> Subject: Re: [boost] [VS2017][release] vswhere.exe
>>
>> On 5 April 2017 at 20:23, Tom Kent via Boost <boost_at_[hidden]> 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.
>>
>> To those users that are unable to use google, unable to click a link and
>> download an executable, and those who don't understand what "put the
>> executable in your path" means, the use of most boost libraries is most
>> probably above their pay-grade anyway. You're looking for nails at low
>> tide...
>
> I disagree - MS IDE users expect it all to 'just work' from the IDE.
>
> They rightly don't expect to mess about with funny paths and hideous command windows.

While I generally agree that the simpler installation and use process 
the better, a developer who haven't heard of PATH or command line is not 
a developer.

MS has brought the mess with toolset location on its users. We can do 
only so much to not make things worse from our end. Giving simple 
instructions to follow is IMHO enough.