Hi,

Visual D does not work with VS 2017. When will there be a fix?

[ VS2917/windows 10 - 64x
  When creating an project, creation fails, nothing is shown
]

On Thursday, 4 May 2017 at 16:25:42 UTC, jj wrote:
> Hi,
>
> Visual D does not work with VS 2017. When will there be a fix?
>
> [ VS2917/windows 10 - 64x
>   When creating an project, creation fails, nothing is shown
> ]

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

On Thursday, 4 May 2017 at 18:20:29 UTC, Jolly James wrote:
> On Thursday, 4 May 2017 at 16:25:42 UTC, jj wrote:
>> Hi,
>>
>> Visual D does not work with VS 2017. When will there be a fix?
>>
>> [ VS2917/windows 10 - 64x
>>   When creating an project, creation fails, nothing is shown
>> ]
>
> 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.

On Friday, 5 May 2017 at 07:14:55 UTC, jj wrote:
> On Thursday, 4 May 2017 at 18:20:29 UTC, Jolly James wrote:
>> On Thursday, 4 May 2017 at 16:25:42 UTC, jj wrote:
>>> Hi,
>>>
>>> Visual D does not work with VS 2017. When will there be a fix?
>>>
>>> [ VS2917/windows 10 - 64x
>>>   When creating an project, creation fails, nothing is shown
>>> ]
>>
>> 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.

visuald does install, but none of the paths is under options changeable. they are empty and grayed out. any solutions to that?

On Saturday, 6 May 2017 at 07:53:11 UTC, jj wrote:
> On Friday, 5 May 2017 at 07:14:55 UTC, jj wrote:
>> On Thursday, 4 May 2017 at 18:20:29 UTC, Jolly James wrote:
>>> On Thursday, 4 May 2017 at 16:25:42 UTC, jj wrote:
>>>> Hi,
>>>>
>>>> Visual D does not work with VS 2017. When will there be a fix?
>>>>
>>>> [ VS2917/windows 10 - 64x
>>>>   When creating an project, creation fails, nothing is shown
>>>> ]
>>>
>>> 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.
>
> visuald does install, but none of the paths is under options changeable. they are empty and grayed out. any solutions to that?

found page "http://rainers.github.io/visuald/visuald/BuildFromSource.html", ran
devenv /RootSuffix D

and it worked

> found page "http://rainers.github.io/visuald/visuald/BuildFromSource.html", ran
> devenv /RootSuffix D
>
> and it worked

after 2-3 stats of visual studio 2017, visuald quit and is not visable anymore.

> found page "http://rainers.github.io/visuald/visuald/BuildFromSource.html", ran
> devenv /RootSuffix D
>
> and it worked

after 2-3 stats of visual studio 2017, visuald quit and is not visable anymore.

On 07.05.2017 09:47, jj wrote:
>> found page
>> "http://rainers.github.io/visuald/visuald/BuildFromSource.html", ran
>> devenv /RootSuffix D
>>
>> and it worked

For VS 2015 or earlier this creates a new hive in the user registry that is populated with a clean copy of the system hive (HKEY_LOCAL_MACHINE). For VS2017 this has been moved to a private registry file.

>
> after 2-3 stats of visual studio 2017, visuald quit and is not visable
> anymore.

Whenever VS feels like there has been some change to the installation, it will reinitialize the user registry. Maybe there is something wrong there.

You might find some error message when starting devenv with logging "devenv /log". This will write

c:\Users\<username>\AppData\Roaming\Microsoft\VisualStudio\15.0_ade21380\ActivityLog.xml 


that you can inspect with a browser. (Not sure if 15.0_ade21380 is the same for you here).

On Sunday, 7 May 2017 at 15:00:52 UTC, Rainer Schuetze wrote:
>
>
> On 07.05.2017 09:47, jj wrote:
>>> [...]
>
> For VS 2015 or earlier this creates a new hive in the user registry that is populated with a clean copy of the system hive (HKEY_LOCAL_MACHINE). For VS2017 this has been moved to a private registry file.
>
>>
>> after 2-3 stats of visual studio 2017, visuald quit and is not visable
>> anymore.
>
> Whenever VS feels like there has been some change to the installation, it will reinitialize the user registry. Maybe there is something wrong there.
>
> You might find some error message when starting devenv with logging "devenv /log". This will write
>
> c:\Users\<username>\AppData\Roaming\Microsoft\VisualStudio\15.0_ade21380\ActivityLog.xml
>
>
> that you can inspect with a browser. (Not sure if 15.0_ade21380 is the same for you here).

did that, but could not find any error message

On Sunday, 7 May 2017 at 16:53:03 UTC, jj wrote:
> On Sunday, 7 May 2017 at 15:00:52 UTC, Rainer Schuetze wrote:
>> [...]
>
> did that, but could not find any error message

another info:
with right click project i get visuald and can change settings.
only for ldc (newest beta version) i can not debug.