I just installed DMD and Visual D.
Whenever I press F5, even if I did not make changes to the project, I keep getting prompted to rebuild. Build log shows:

Debug\Sandbox1.exe not up to date: link dependency file ~\Documents\Visual Studio 2013\Projects\Sandbox1\Sandbox1\Debug\Sandbox1.lnkdep does not exist
------ Build started: Project: Sandbox1, Configuration: Debug Win32 ------
Building Debug\Sandbox1.exe...
Debug\Sandbox1.exe not up to date: link dependency file ~\Documents\Visual Studio 2013\Projects\Sandbox1\Sandbox1\Debug\Sandbox1.lnkdep does not exist
Converting debug information...
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

I'm using Visual Studio 2013 (isolated and integrated shell installs) on a 64-bit Windows.

Any ideas on why this is happening? Do I have to change some sort of setting.

On 25.10.2014 19:50, IK wrote:
> I just installed DMD and Visual D.
> Whenever I press F5, even if I did not make changes to the project, I
> keep getting prompted to rebuild. Build log shows:
>
> Debug\Sandbox1.exe not up to date: link dependency file
> ~\Documents\Visual Studio
> 2013\Projects\Sandbox1\Sandbox1\Debug\Sandbox1.lnkdep does not exist
> ------ Build started: Project: Sandbox1, Configuration: Debug Win32 ------
> Building Debug\Sandbox1.exe...
> Debug\Sandbox1.exe not up to date: link dependency file
> ~\Documents\Visual Studio
> 2013\Projects\Sandbox1\Sandbox1\Debug\Sandbox1.lnkdep does not exist
> Converting debug information...
> ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
>
> I'm using Visual Studio 2013 (isolated and integrated shell installs) on
> a 64-bit Windows.
>
> Any ideas on why this is happening? Do I have to change some sort of
> setting.

That's a bug in the dependency tracker utility. The new beta should have that fixed: https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.40-beta1