On Monday, 1 December 2014 at 06:15:43 UTC, sdvcn wrote:
> 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
>      |

Proposal:
Pdb file should be included with the release package.

On 01.12.2014 07:25, sdvcn wrote:
> On Monday, 1 December 2014 at 06:15:43 UTC, sdvcn wrote:
>> 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
>>      |
>
> Proposal:
> Pdb file should be included with the release package.

I cannot build the release version of Visual D with debug info anymore, optlink fails to build with "too much debug info". That's why I have given up on supplying pdb files.

The filemonitor.dll could be built with debug info, but I don't think it reveal anything. I guess your system somehow disables DLL injection (a technique which might also be abused by viruses).

You can disable the use of this DLL by unchecking "Monitor optlink dependencies" on the Tools->Options->Projects and Solutions->Visual D Settings page.