• jj (1/1) May 04 2017 the installer does not work for VS 2017 - that sucks!!!
• Jolly James (3/4) May 04 2017 see also:
• jj (4/8) May 05 2017 after watching dconf a bit, wanting to try it, i give up right
• Jesse Phillips (6/16) May 05 2017 I can understand waiting until support for your environment is

jj <jj aol.com> writes:

the installer does not work for VS 2017 - that sucks!!!

Jolly James <j.j jmail.com> writes:

On Thursday, 4 May 2017 at 16:43:27 UTC, jj wrote:
 the installer does not work for VS 2017 - that sucks!!!

see also: 
https://forum.dlang.org/post/oe7usu$bvf$1 digitalmars.com

jj <jj aol.com> writes:

On Thursday, 4 May 2017 at 18:21:58 UTC, Jolly James wrote:
 On Thursday, 4 May 2017 at 16:43:27 UTC, jj wrote:
 the installer does not work for VS 2017 - that sucks!!!

 see also: 
 https://forum.dlang.org/post/oe7usu$bvf$1 digitalmars.com

after watching dconf a bit, wanting to try it, i give up right 
now.
useless if you can't install and who knows what else doesn't work.

Jesse Phillips <Jesse.K.Phillips+D gmail.com> writes:

On Friday, 5 May 2017 at 07:14:35 UTC, jj wrote:
 On Thursday, 4 May 2017 at 18:21:58 UTC, Jolly James wrote:
 On Thursday, 4 May 2017 at 16:43:27 UTC, jj wrote:
 the installer does not work for VS 2017 - that sucks!!!

 see also: 
 https://forum.dlang.org/post/oe7usu$bvf$1 digitalmars.com

 after watching dconf a bit, wanting to try it, i give up right 
 now.
 useless if you can't install and who knows what else doesn't 
 work.

I can understand waiting until support for your environment is 
implemented before using something, but to then associate that 
lack of support with other parts not working is absurd. "Visual 
Studio 2017 can't install on my Linux machine, who knows what 
else is broken in this IDE?"