December 21, 2015
I created a new D project and added some source code from a git package which just contained a lot of d files in various sub-dirs. I did this so I could view the code in with proper highlighting and useful searching features. I simply dragged the files into the solution and VS shows them. I can double click and view any file.

Unfortunately the code doesn't compile(the hello works main.d) as it says it can't find dmc. Not sure why it needs dmc...

Anyways, I don't care about compilation. I just want to use "find all references", "goto definition", etc... But they don't return any results... even if there are multiple references in the same file.

Any ideas why these search features won't work? Does the project have to be compiled?

December 22, 2015

On 21.12.2015 20:52, Jason Alexander wrote:
> I created a new D project and added some source code from a git package
> which just contained a lot of d files in various sub-dirs. I did this so
> I could view the code in with proper highlighting and useful searching
> features. I simply dragged the files into the solution and VS shows
> them. I can double click and view any file.
>
> Unfortunately the code doesn't compile(the hello works main.d) as it
> says it can't find dmc. Not sure why it needs dmc...

That suggests that there is some C code mixed into the other source. dmc is invoked by Visual D to compile .c or .cpp files for Win32.

>
> Anyways, I don't care about compilation. I just want to use "find all
> references", "goto definition", etc... But they don't return any
> results... even if there are multiple references in the same file.
>
> Any ideas why these search features won't work? Does the project have to
> be compiled?
>

"Find all references" is not yet fully implemented, so expect some hickups. "Goto definition" should work, though the semantic analysis still needs to be able to make sense of the code, which is close to compiling it. It is not as picky as the compiler, so an error in some places should not affect everything else.

One idea: maybe imports are not found with the given import paths. Try to set these correctly in the Visual D project settings.