• jj (5/5) May 04 2017 Hi,
• Jolly James (3/8) May 04 2017 see also:
• jj (4/14) May 05 2017 after watching dconf a bit, wanting to try it, i give up right
• jj (3/19) May 06 2017 visuald does install, but none of the paths is under options
• jj (6/28) May 06 2017 found page
• jj (2/6) May 07 2017 after 2-3 stats of visual studio 2017, visuald quit and is not
• Rainer Schuetze (12/19) May 07 2017 For VS 2015 or earlier this creates a new hive in the user registry that...
• jj (2/20) May 07 2017 did that, but could not find any error message
• jj (4/7) May 07 2017 another info:
• Rainer Schuetze (5/13) May 08 2017 Ok, I guess Visual D is working now in general.
• jj (19/33) May 09 2017 dmd works in release and debug. as for ldc debug:
• jj (31/69) May 09 2017 file content:
• Rainer Schuetze (7/36) May 09 2017 That's the same problem as in the bug report. Please change the
• jj (5/37) May 11 2017 thanks for the advice. i try that, but clicking on LDC tells me
• jj (4/12) May 09 2017 kasperski started to recognize visualD.dll as
• Rainer Schuetze (7/19) May 09 2017 I haven't heard about this for VisualD.dll, but there was recently a
• jj (2/6) May 07 2017 after 2-3 stats of visual studio 2017, visuald quit and is not

jj <jj aol.com> writes:

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
]

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

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

jj <jj aol.com> writes:

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.

jj <jj aol.com> writes:

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?

jj <jj aol.com> writes:

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

jj <jj aol.com> writes:

 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.

Rainer Schuetze <r.sagitario gmx.de> writes:

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_ade2
380\ActivityLog.xml 


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

jj <jj aol.com> writes:

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

jj <jj aol.com> writes:

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.

Rainer Schuetze <r.sagitario gmx.de> writes:

On 07.05.2017 19:08, jj wrote:
 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.

Ok, I guess Visual D is working now in general.

With LDC you might be running into 
https://issues.dlang.org/show_bug.cgi?id=17384. if not, please provide a 
few more details.

jj <jj aol.com> writes:

On Tuesday, 9 May 2017 at 06:52:14 UTC, Rainer Schuetze wrote:
 On 07.05.2017 19:08, jj wrote:
 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.

 Ok, I guess Visual D is working now in general.

 With LDC you might be running into 
 https://issues.dlang.org/show_bug.cgi?id=17384. if not, please 
 provide a few more details.

dmd works in release and debug. as for ldc debug:

Building x64\Debug LDC\ConsoleApp1.exe...
LINK : fatal error LNK1171: mspdb140.dll kann nicht geladen 
werden (Fehlercode: 193)
Error: C:\Program Files (x86)\Microsoft Visual 
Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\link.exe failed
with status: 1171
Building x64\Debug LDC\ConsoleApp1.exe failed!
Details saved as 
"file://H:\DSOURCE\ConsoleApp1\ConsoleApp1\x64\Debug%20LDC\ConsoleApp1.buildlog.html"

ldc release:

Building x64\Release LDC\ConsoleApp1.exe...
LINK : fatal error LNK1171: mspdb140.dll kann nicht geladen 
werden (Fehlercode: 193)
Error: C:\Program Files (x86)\Microsoft Visual 
Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\link.exe failed
with status: 1171
Building x64\Release LDC\ConsoleApp1.exe failed!
Details saved as 
"file://H:\DSOURCE\ConsoleApp1\ConsoleApp1\x64\Release%20LDC\ConsoleApp1.buildlog.html"

jj <jj aol.com> writes:

On Tuesday, 9 May 2017 at 07:43:54 UTC, jj wrote:
 On Tuesday, 9 May 2017 at 06:52:14 UTC, Rainer Schuetze wrote:
 On 07.05.2017 19:08, jj wrote:
 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.

 Ok, I guess Visual D is working now in general.

 With LDC you might be running into 
 https://issues.dlang.org/show_bug.cgi?id=17384. if not, please 
 provide a few more details.

 dmd works in release and debug. as for ldc debug:

 Building x64\Debug LDC\ConsoleApp1.exe...
 LINK : fatal error LNK1171: mspdb140.dll kann nicht geladen 
 werden (Fehlercode: 193)
 Error: C:\Program Files (x86)\Microsoft Visual 
 Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\link.exe
failed with status: 1171
 Building x64\Debug LDC\ConsoleApp1.exe failed!
 Details saved as 
 "file://H:\DSOURCE\ConsoleApp1\ConsoleApp1\x64\Debug%20LDC\ConsoleApp1.buildlog.html"

 ldc release:

 Building x64\Release LDC\ConsoleApp1.exe...
 LINK : fatal error LNK1171: mspdb140.dll kann nicht geladen 
 werden (Fehlercode: 193)
 Error: C:\Program Files (x86)\Microsoft Visual 
 Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\link.exe
failed with status: 1171
 Building x64\Release LDC\ConsoleApp1.exe failed!
 Details saved as 
 "file://H:\DSOURCE\ConsoleApp1\ConsoleApp1\x64\Release%20LDC\ConsoleApp1.buildlog.html"

file content:


Command Line

set PATH=E:\D\ldc2\bin;C:\Program Files (x86)\Microsoft Visual 
Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64;bin;%PATH%
set LIB=C:\Program Files (x86)\Microsoft Visual 
Studio\2017\Community\VC\Tools\MSVC\14.10.25017\lib\x64;C:\Program Files
(x86)\Windows Kits\10\Lib\10.0.15063.0\ucrt\x64
set VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual 
Studio\2017\Community\VC\
set VCTOOLSINSTALLDIR=C:\Program Files (x86)\Microsoft Visual 
Studio\2017\Community\VC\Tools\MSVC\14.10.25017\
set VSINSTALLDIR=C:\Program Files (x86)\Microsoft Visual 
Studio\2017\Community\
"C:\Program Files (x86)\VisualD\pipedmd.exe" ldc2 -m64 -O 
-release -X -Xf="x64\Release LDC\ConsoleApp1.json" 
-deps="x64\Release LDC\ConsoleApp1.dep" -of="x64\Release 
LDC\ConsoleApp1.exe" -L/MAP:"x64\Release LDC\ConsoleApp1.map" 
main.d
if errorlevel 1 goto reportError
if not exist "x64\Release LDC\ConsoleApp1.exe" (echo "x64\Release 
LDC\ConsoleApp1.exe" not created! && goto reportError)

goto noError

:reportError
echo Building x64\Release LDC\ConsoleApp1.exe failed!

:noError
Output

LINK : fatal error LNK1171: mspdb140.dll kann nicht geladen 
werden (Fehlercode: 193)
Error: C:\Program Files (x86)\Microsoft Visual 
Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\link.exe failed
with status: 1171
Building x64\Release LDC\ConsoleApp1.exe failed!

Rainer Schuetze <r.sagitario gmx.de> writes:

On 09.05.2017 09:43, jj wrote:
 On Tuesday, 9 May 2017 at 06:52:14 UTC, Rainer Schuetze wrote:
 On 07.05.2017 19:08, jj wrote:
 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.

 Ok, I guess Visual D is working now in general.

 With LDC you might be running into
 https://issues.dlang.org/show_bug.cgi?id=17384. if not, please provide
 a few more details.

 dmd works in release and debug. as for ldc debug:

 Building x64\Debug LDC\ConsoleApp1.exe...
 LINK : fatal error LNK1171: mspdb140.dll kann nicht geladen werden
 (Fehlercode: 193)
 Error: C:\Program Files (x86)\Microsoft Visual
 Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\link.exe
 failed with status: 1171
 Building x64\Debug LDC\ConsoleApp1.exe failed!
 Details saved as
 "file://H:\DSOURCE\ConsoleApp1\ConsoleApp1\x64\Debug%20LDC\ConsoleApp1.buildlog.html"

That's the same problem as in the bug report. Please change the 
executable search paths in Tools->Options->Projects and 
Solutions->Visual D Settings->LDC->x64 from

$(VCTOOLSINSTALLDIR)bin\HostX86\x64

to

$(VCTOOLSINSTALLDIR)bin\HostX64\x64

jj <jj aol.com> writes:

On Tuesday, 9 May 2017 at 19:19:24 UTC, Rainer Schuetze wrote:
 On 09.05.2017 09:43, jj wrote:
 On Tuesday, 9 May 2017 at 06:52:14 UTC, Rainer Schuetze wrote:
 On 07.05.2017 19:08, jj wrote:
 [...]

 Ok, I guess Visual D is working now in general.

 With LDC you might be running into
 https://issues.dlang.org/show_bug.cgi?id=17384. if not, 
 please provide
 a few more details.

 dmd works in release and debug. as for ldc debug:

 Building x64\Debug LDC\ConsoleApp1.exe...
 LINK : fatal error LNK1171: mspdb140.dll kann nicht geladen 
 werden
 (Fehlercode: 193)
 Error: C:\Program Files (x86)\Microsoft Visual
 Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\link.exe
 failed with status: 1171
 Building x64\Debug LDC\ConsoleApp1.exe failed!
 Details saved as
 "file://H:\DSOURCE\ConsoleApp1\ConsoleApp1\x64\Debug%20LDC\ConsoleApp1.buildlog.html"

 That's the same problem as in the bug report. Please change the 
 executable search paths in Tools->Options->Projects and 
 Solutions->Visual D Settings->LDC->x64 from

 $(VCTOOLSINSTALLDIR)bin\HostX86\x64

 to

 $(VCTOOLSINSTALLDIR)bin\HostX64\x64

thanks for the advice. i try that, but clicking on LDC tells me 
that that the visual d package was loaded properly.

well i think, i give up for now and wait for some future updates.
thank you very much for your care.

jj <jj aol.com> writes:

On Sunday, 7 May 2017 at 17:08:15 UTC, jj wrote:
 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.

kasperski started to recognize visualD.dll as 
Trojan.Win32.Generic. any experiences with other 
antivirus-software?

Rainer Schuetze <r.sagitario gmx.de> writes:

On 09.05.2017 10:24, jj wrote:
 On Sunday, 7 May 2017 at 17:08:15 UTC, jj wrote:
 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.

 kasperski started to recognize visualD.dll as Trojan.Win32.Generic. any
 experiences with other antivirus-software?

I haven't heard about this for VisualD.dll, but there was recently a 
report that dmd.exe is reported as malware by some AV software. I 
suspect it has to do with something in the runtime library that is 
linked in by both.

Trying it on www.virustotal.com, VisualD.dll is flagged by 3/59 
scanners, but some more obscure ones.

jj <jj aol.com> writes:

 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.