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.

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"

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!

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?

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

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.

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.