Hi everyone,

I'm experiencing a bit of trouble getting Visual D to work for
me. Here's where I'm at:

OS: Windows 8.1
DMD: 2.066.1
Visual Studio 2013 Professional
Visual D: 0.3.40 Beta 2 (tried 0.3.39 as well)

--------- Attempt 1 ---------
When I build with Visual D using the defaults (override sc.ini
checked):

------ Build started: Project: test64, Configuration: Debug DMD
x64 ------
Building Debug DMD x64\test64.exe...
LINK : fatal error LNK1181: cannot open input file 'DMD.obj'
Building Debug DMD x64\test64.exe failed!
Details saved as "file://S:\D\Dev\test64\test64\Debug DMD
x64\test64.buildlog.html"
Build time: 1 s
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped
==========

Build Log
Building Debug DMD x64\test64.exe
Command Line
set PATH=S:\D\Tools\dmd2\windows\bin;C:\Program Files
(x86)\Windows Kits\8.1\\bin\x64;%PATH%
set DMD_LIB=C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\\lib\amd64;C:\Program Files (x86)\Windows
Kits\8.1\Lib\winv6.3\um\x64
set WindowsSdkDir=C:\Program Files (x86)\Windows Kits\8.1\
set VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\
dmd -m64 -g -debug -X -Xf"Debug DMD x64\test64.json" -deps="Debug
DMD x64\test64.dep" -c -of"Debug DMD x64\test64.obj" main.d
if errorlevel 1 goto reportError

set LIB="S:\D\Tools\dmd2\windows\bin\..\lib64";"C:\Program Files
(x86)\Microsoft Visual Studio 12.0\VC\\lib\amd64";"C:\Program
Files (x86)\Windows Kits\8.1\\Lib\winv6.3\um\x64";"C:\Program
Files (x86)\Windows Kits\8.1\\Lib\win8\um\x64";"C:\Program Files
(x86)\Windows Kits\8.1\\Lib\x64"
echo. > S:\D\Dev\test64\test64\Debug DMD x64\test64.build.lnkarg
echo "Debug DMD x64\test64.obj" /OUT:"Debug DMD x64\test64.exe"
/MAP:"Debug DMD x64\test64.map" user32.lib kernel32.lib
/LIBPATH:"C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\\lib\amd64" /LIBPATH:"C:\Program Files (x86)\Windows
Kits\8.1\Lib\winv6.3\um\x64" /DEBUG /INCREMENTAL:NO /NOLOGO >>
S:\D\Dev\test64\test64\Debug DMD x64\test64.build.lnkarg

"C:\Program Files (x86)\VisualD\pipedmd.exe" -deps "Debug DMD
x64\test64.lnkdep" "C:\Program Files (x86)\Microsoft Visual
Studio 12.0\VC\\bin\link.exe" @S:\D\Dev\test64\test64\Debug DMD
x64\test64.build.lnkarg
if errorlevel 1 goto reportError
if not exist "Debug DMD x64\test64.exe" (echo "Debug DMD
x64\test64.exe" not created! && goto reportError)

goto noError

:reportError
echo Building Debug DMD x64\test64.exe failed!

:noError
Output
LINK : fatal error LNK1181: cannot open input file 'DMD.obj'
Building Debug DMD x64\test64.exe failed!

--------- Attempt 2 ---------
When I build with Visual D with the override sc.ini unchecked,
and sc.ini on install defaults:

------ Build started: Project: test64, Configuration: Debug DMD
x64 ------
Building Debug DMD x64\test64.exe...
LINK : fatal error LNK1171: unable to load mspdb120.dll (error
code: 126)
Building Debug DMD x64\test64.exe failed!
Details saved as "file://S:\D\Dev\test64\test64\Debug DMD
x64\test64.buildlog.html"
Build time: 1 s
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped
==========
Build Log
Building Debug DMD x64\test64.exe
Command Line
set PATH=S:\D\Tools\dmd2\windows\bin;C:\Program Files
(x86)\Windows Kits\8.1\\bin\x64;%PATH%
set DMD_LIB=C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\\lib\amd64;C:\Program Files (x86)\Windows
Kits\8.1\Lib\winv6.3\um\x64
set WindowsSdkDir=C:\Program Files (x86)\Windows Kits\8.1\
set VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\
dmd -m64 -g -debug -X -Xf"Debug DMD x64\test64.json" -deps="Debug
DMD x64\test64.dep" -c -of"Debug DMD x64\test64.obj" main.d
if errorlevel 1 goto reportError

set LIB="S:\D\Tools\dmd2\windows\bin\..\lib64";"C:\Program Files
(x86)\Microsoft Visual Studio 12.0\VC\\lib\amd64";"C:\Program
Files (x86)\Windows Kits\8.1\\Lib\winv6.3\um\x64";"C:\Program
Files (x86)\Windows Kits\8.1\\Lib\win8\um\x64";"C:\Program Files
(x86)\Windows Kits\8.1\\Lib\x64"
echo. > S:\D\Dev\test64\test64\Debug DMD x64\test64.build.lnkarg
echo "Debug DMD x64\test64.obj" /OUT:"Debug DMD x64\test64.exe"
/MAP:"Debug DMD x64\test64.map" user32.lib kernel32.lib
/LIBPATH:"C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\\lib\amd64" /LIBPATH:"C:\Program Files (x86)\Windows
Kits\8.1\Lib\winv6.3\um\x64" /DEBUG /INCREMENTAL:NO /NOLOGO
/OPT:NOICF >> S:\D\Dev\test64\test64\Debug DMD
x64\test64.build.lnkarg

"C:\Program Files (x86)\VisualD\pipedmd.exe" -deps "Debug DMD
x64\test64.lnkdep" "C:\Program Files (x86)\Microsoft Visual
Studio 12.0\VC\\bin\x86_amd64\link.exe"
@S:\D\Dev\test64\test64\Debug DMD x64\test64.build.lnkarg
if errorlevel 1 goto reportError
if not exist "Debug DMD x64\test64.exe" (echo "Debug DMD
x64\test64.exe" not created! && goto reportError)

goto noError

:reportError
echo Building Debug DMD x64\test64.exe failed!

:noError
Output
LINK : fatal error LNK1171: unable to load mspdb120.dll (error
code: 126)
Building Debug DMD x64\test64.exe failed!


--------- Attempt 3 ---------
When I build with Visual D with the override sc.ini unchecked,
and sc.ini using the VC2010 path:

------ Build started: Project: test64, Configuration: Debug DMD
x64 ------
Building Debug DMD x64\test64.exe...
LINK : fatal error LNK1181: cannot open input file 'DMD.obj'
Building Debug DMD x64\test64.exe failed!
Details saved as "file://S:\D\Dev\test64\test64\Debug DMD
x64\test64.buildlog.html"
Build time: 2 s
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped
==========

Build Log
Building Debug DMD x64\test64.exe
Command Line
set PATH=S:\D\Tools\dmd2\windows\bin;C:\Program Files
(x86)\Windows Kits\8.1\\bin\x64;%PATH%
set DMD_LIB=C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\\lib\amd64;C:\Program Files (x86)\Windows
Kits\8.1\Lib\winv6.3\um\x64
set WindowsSdkDir=C:\Program Files (x86)\Windows Kits\8.1\
set VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\
dmd -m64 -g -debug -X -Xf"Debug DMD x64\test64.json" -deps="Debug
DMD x64\test64.dep" -c -of"Debug DMD x64\test64.obj" main.d
if errorlevel 1 goto reportError

set LIB="S:\D\Tools\dmd2\windows\bin\..\lib64";"C:\Program Files
(x86)\Microsoft Visual Studio 12.0\VC\\lib\amd64";"C:\Program
Files (x86)\Windows Kits\8.1\\Lib\winv6.3\um\x64";"C:\Program
Files (x86)\Windows Kits\8.1\\Lib\win8\um\x64";"C:\Program Files
(x86)\Windows Kits\8.1\\Lib\x64"
echo. > S:\D\Dev\test64\test64\Debug DMD x64\test64.build.lnkarg
echo "Debug DMD x64\test64.obj" /OUT:"Debug DMD x64\test64.exe"
/MAP:"Debug DMD x64\test64.map" user32.lib kernel32.lib
/LIBPATH:"C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\\lib\amd64" /LIBPATH:"C:\Program Files (x86)\Windows
Kits\8.1\Lib\winv6.3\um\x64" /DEBUG /INCREMENTAL:NO /NOLOGO
/OPT:NOICF >> S:\D\Dev\test64\test64\Debug DMD
x64\test64.build.lnkarg

"C:\Program Files (x86)\VisualD\pipedmd.exe" -deps "Debug DMD
x64\test64.lnkdep" "C:\Program Files (x86)\Microsoft Visual
Studio 12.0\VC\\bin\amd64\link.exe" @S:\D\Dev\test64\test64\Debug
DMD x64\test64.build.lnkarg
if errorlevel 1 goto reportError
if not exist "Debug DMD x64\test64.exe" (echo "Debug DMD
x64\test64.exe" not created! && goto reportError)

goto noError

:reportError
echo Building Debug DMD x64\test64.exe failed!

:noError
Output
LINK : fatal error LNK1181: cannot open input file 'DMD.obj'
Building Debug DMD x64\test64.exe failed!

I reinstalled both DMD and Visual D to make sure it wasn't
something silly I changed. Still no luck.

Any ideas?

Thanks,
Charles

I went ahead and made a forum account, I'm Charles from above.

On 14.11.2014 05:54, Charles wrote:
> echo "Debug DMD x64\test64.obj" /OUT:"Debug DMD x64\test64.exe"
> /MAP:"Debug DMD x64\test64.map" user32.lib kernel32.lib
> /LIBPATH:"C:\Program Files (x86)\Microsoft Visual Studio
> 12.0\VC\\lib\amd64" /LIBPATH:"C:\Program Files (x86)\Windows
> Kits\8.1\Lib\winv6.3\um\x64" /DEBUG /INCREMENTAL:NO /NOLOGO >>
> S:\D\Dev\test64\test64\Debug DMD x64\test64.build.lnkarg

There are obviously quotes missing for the .lnkarg file that contains "Debug DMD x64". I'll look into this.

As a workaround, please rename the configuration to something that doesn't contain spaces.

On Friday, 14 November 2014 at 11:13:32 UTC, Rainer Schuetze
wrote:

> As a workaround, please rename the configuration to something that doesn't contain spaces.

I thought that's what the issue was; however, I'm not sure where
to update the config at.

On 14.11.2014 16:33, Charles wrote:
> On Friday, 14 November 2014 at 11:13:32 UTC, Rainer Schuetze
> wrote:
>
>> As a workaround, please rename the configuration to something that
>> doesn't contain spaces.
>
> I thought that's what the issue was; however, I'm not sure where
> to update the config at.

Go to the configuration manager, select the project configuration and click "Edit" in the drop-down list. The following dialog allows renaming...

On Friday, 14 November 2014 at 17:14:25 UTC, Rainer Schuetze wrote:
>
>
> On 14.11.2014 16:33, Charles wrote:
>> On Friday, 14 November 2014 at 11:13:32 UTC, Rainer Schuetze
>> wrote:
>>
>>> As a workaround, please rename the configuration to something that
>>> doesn't contain spaces.
>>
>> I thought that's what the issue was; however, I'm not sure where
>> to update the config at.
>
> Go to the configuration manager, select the project configuration and click "Edit" in the drop-down list. The following dialog allows renaming...

日志名称:          Application
来源:            Application Error
日期:            2014/11/20 15:44:13
事件 ID:         1000
任务类别:          (100)
级别:            错误
关键字:           经典
用户:            暂缺
计算机:           WIN-6RRLID41QMM
描述:
错误应用程序名称: link.exe，版本: 12.0.30324.0，时间戳: 0x532f655e
错误模块名称: filemonitor.dll，版本: 0.0.0.0，时间戳: 0x00000000
异常代码: 0xc0000005
错误偏移量: 0x0000309b
错误进程 ID: 0xd70
错误应用程序启动时间: 0x01d00495ab86ed5a
错误应用程序路径: C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\link.exe
错误模块路径: C:\Program Files (x86)\VisualD\filemonitor.dll
报告 ID: 04e0d41e-7089-11e4-ae24-00e066349802


filemonitor.dll error

https://github.com/D-Programming-Language/visuald/raw/master/tools/filemonitor.d
Compile replacement

On 20.11.2014 09:27, sdvcn wrote:
> On Friday, 14 November 2014 at 17:14:25 UTC, Rainer Schuetze wrote:
>>
>>
>> On 14.11.2014 16:33, Charles wrote:
>>> On Friday, 14 November 2014 at 11:13:32 UTC, Rainer Schuetze
>>> wrote:
>>>
>>>> As a workaround, please rename the configuration to something that
>>>> doesn't contain spaces.
>>>
>>> I thought that's what the issue was; however, I'm not sure where
>>> to update the config at.
>>
>> Go to the configuration manager, select the project configuration and
>> click "Edit" in the drop-down list. The following dialog allows
>> renaming...
>
> 日志名称:          Application
> 来源:            Application Error
> 日期:            2014/11/20 15:44:13
> 事件 ID:         1000
> 任务类别:          (100)
> 级别:            错误
> 关键字:           经典
> 用户:            暂缺
> 计算机:           WIN-6RRLID41QMM
> 描述:
> 错误应用程序名称: link.exe，版本: 12.0.30324.0，时间戳: 0x532f655e
> 错误模块名称: filemonitor.dll，版本: 0.0.0.0，时间戳: 0x00000000
> 异常代码: 0xc0000005
> 错误偏移量: 0x0000309b
> 错误进程 ID: 0xd70
> 错误应用程序启动时间: 0x01d00495ab86ed5a
> 错误应用程序路径: C:\Program Files (x86)\Microsoft Visual Studio
> 12.0\VC\bin\link.exe
> 错误模块路径: C:\Program Files (x86)\VisualD\filemonitor.dll
> 报告 ID: 04e0d41e-7089-11e4-ae24-00e066349802
>
>
> filemonitor.dll error
>
> https://github.com/D-Programming-Language/visuald/raw/master/tools/filemonitor.d
>
> Compile replacement
>

I can't really decipher this but I guess it's some kind of crash report.

There have been some recent fixes to the file monitor. Have you tried one of the latest betas: https://github.com/D-Programming-Language/visuald/releases ?

On Saturday, 22 November 2014 at 10:17:59 UTC, Rainer Schuetze wrote:
>
>
> On 20.11.2014 09:27, sdvcn wrote:
>> On Friday, 14 November 2014 at 17:14:25 UTC, Rainer Schuetze wrote:
>>>
>>>
>>> On 14.11.2014 16:33, Charles wrote:
>>>> On Friday, 14 November 2014 at 11:13:32 UTC, Rainer Schuetze
>>>> wrote:
>>>>
>>>>> As a workaround, please rename the configuration to something that
>>>>> doesn't contain spaces.
>>>>
>>>> I thought that's what the issue was; however, I'm not sure where
>>>> to update the config at.
>>>
>>> Go to the configuration manager, select the project configuration and
>>> click "Edit" in the drop-down list. The following dialog allows
>>> renaming...
>>
>> 日志名称:          Application
>> 来源:            Application Error
>> 日期:            2014/11/20 15:44:13
>> 事件 ID:         1000
>> 任务类别:          (100)
>> 级别:            错误
>> 关键字:           经典
>> 用户:            暂缺
>> 计算机:           WIN-6RRLID41QMM
>> 描述:
>> 错误应用程序名称: link.exe，版本: 12.0.30324.0，时间戳: 0x532f655e
>> 错误模块名称: filemonitor.dll，版本: 0.0.0.0，时间戳: 0x00000000
>> 异常代码: 0xc0000005
>> 错误偏移量: 0x0000309b
>> 错误进程 ID: 0xd70
>> 错误应用程序启动时间: 0x01d00495ab86ed5a
>> 错误应用程序路径: C:\Program Files (x86)\Microsoft Visual Studio
>> 12.0\VC\bin\link.exe
>> 错误模块路径: C:\Program Files (x86)\VisualD\filemonitor.dll
>> 报告 ID: 04e0d41e-7089-11e4-ae24-00e066349802
>>
>>
>> filemonitor.dll error
>>
>> https://github.com/D-Programming-Language/visuald/raw/master/tools/filemonitor.d
>>
>> Compile replacement
>>
>
> I can't really decipher this but I guess it's some kind of crash report.
>
> There have been some recent fixes to the file monitor. Have you tried one of the latest betas: https://github.com/D-Programming-Language/visuald/releases ?

(Visual D v0.3.40 beta 2) This package filemonitor.dll file is wrong.

On 23.11.2014 00:02, sdvcn wrote:
> On Saturday, 22 November 2014 at 10:17:59 UTC, Rainer Schuetze wrote:
>>
>>
>> On 20.11.2014 09:27, sdvcn wrote:
>>> On Friday, 14 November 2014 at 17:14:25 UTC, Rainer Schuetze wrote:
>>>>
>>>>
>>>> On 14.11.2014 16:33, Charles wrote:
>>>>> On Friday, 14 November 2014 at 11:13:32 UTC, Rainer Schuetze
>>>>> wrote:
>>>>>
>>>>>> As a workaround, please rename the configuration to something that
>>>>>> doesn't contain spaces.
>>>>>
>>>>> I thought that's what the issue was; however, I'm not sure where
>>>>> to update the config at.
>>>>
>>>> Go to the configuration manager, select the project configuration and
>>>> click "Edit" in the drop-down list. The following dialog allows
>>>> renaming...
>>>
>>> 日志名称:          Application
>>> 来源:            Application Error
>>> 日期:            2014/11/20 15:44:13
>>> 事件 ID:         1000
>>> 任务类别:          (100)
>>> 级别:            错误
>>> 关键字:           经典
>>> 用户:            暂缺
>>> 计算机:           WIN-6RRLID41QMM
>>> 描述:
>>> 错误应用程序名称: link.exe，版本: 12.0.30324.0，时间戳: 0x532f655e
>>> 错误模块名称: filemonitor.dll，版本: 0.0.0.0，时间戳: 0x00000000
>>> 异常代码: 0xc0000005
>>> 错误偏移量: 0x0000309b
>>> 错误进程 ID: 0xd70
>>> 错误应用程序启动时间: 0x01d00495ab86ed5a
>>> 错误应用程序路径: C:\Program Files (x86)\Microsoft Visual Studio
>>> 12.0\VC\bin\link.exe
>>> 错误模块路径: C:\Program Files (x86)\VisualD\filemonitor.dll
>>> 报告 ID: 04e0d41e-7089-11e4-ae24-00e066349802
>>>
>>>
>>> filemonitor.dll error
>>>
>>> https://github.com/D-Programming-Language/visuald/raw/master/tools/filemonitor.d
>>>
>>>
>>> Compile replacement
>>>
>>
>> I can't really decipher this but I guess it's some kind of crash report.
>>
>> There have been some recent fixes to the file monitor. Have you tried
>> one of the latest betas:
>> https://github.com/D-Programming-Language/visuald/releases ?
>
> (Visual D v0.3.40 beta 2) This package filemonitor.dll file is wrong.

I'm not sure what's wrong with it. It is known to be reported by some Anti-Virus programs because it is injected into the linker process, though. Is this the issue here?

Compile filemonitor.dll No problem
(https://github.com/D-Programming-Language/visuald/raw/master/tools/filemonitor.d)

Visual C++ 2013   06181-004-0451047-02659
DMD32 D Compiler v2.066.1
Microsoft Windows [ver 6.1.7601] windows 2008r2
no Anti-Virus programs .

(Compare file PE)
                         | (0.3.40b3)           | my filemonitor       |
AddressOfEntryPoint      | 00003000             | 00000000             |