I guess you are referring to the VC project integration.

On 05/02/2022 20:06, frame wrote:
> Should the "Import paths" setting in Visual D settings (DMD Directories) be applied to the compiler or has it another purpose?

It only changes the compiler command line.

> In the project properties it has the default value %(ImportPaths) which does nothing to me.
> 
> I do not want to manually specifiy the path for each project in my solution so I currently use a workaround via custom project property sheet where I can set the path for all at once. This sheet also allows to specify user defined variables (macros) (which are missing in the default properties) that can be used in the sheet again.
> 
> I found this workaround very useful, maybe the VisualD docs could mention this?

This is the msbuild way to do this, but I'd consider it slightly advanced usage of it (in contrast to just using the UI - which about 99% of users only know about).

I don't think it makes sense to try to document msbuild, but documentation could emphasize that the VC integration makes all the features of msbuild available.

On Sunday, 6 February 2022 at 07:53:20 UTC, Rainer Schuetze wrote:

> This is the msbuild way to do this, but I'd consider it slightly advanced usage of it (in contrast to just using the UI - which about 99% of users only know about).

Yeah, but users can create the property sheet via UI too - no need to know about the file structure or its content. It can be easily done in the Project Property Manager window. The only task is to create a sheet and adding that existing one to each project.

> I don't think it makes sense to try to document msbuild, but documentation could emphasize that the VC integration makes all the features of msbuild available.

I would expect that every project inherit the path from the Import Paths setting but unfortunately this doesn't work so I think it's worth to mention this workaround.